Popular Games

Symmetrix Configuration Considerations Configure enough resources for your workload Use resources evenly for best overall performance Spread across all available components Includes FE, BE and disks Path management can help FE FAST/Optimizer can help BE Commonly asked questions What size system do I need? Each resource has a limit of I/Os per second and MBs per second Disks Back-end controllers (DAs) Front-end controllers (Fibre, FICON, GigE) SRDF controllers Slices (CPU complexes) Configure enough components to support workload peaks Use those resources as uniformly as possible CPU utilization As a rule of thumb, a limit of no more than 50-70% utilization is good if response time is critical A higher utilization can be tolerated if only IOPS or total throughput matters Memory considerations Ideal to have same size memory boards and same memory between engines Imbalance will make little or no difference with OLTP type workloads Imbalance will create more accesses to boards or engines...

Synergy configuration example For a year or more, I have been using the program called Synergy to control multiple computers from a single machine with a single keyboard and mouse. Synergy is available for most Linux distributions, but it is also interesting to note the original program has not been upgraded since 2006. Synergy+ is a maintenance fork for implementing bug fixes to the original Synergy by Chris Schoeneman, which hasnt any source updates or new releases since 2006 (as of writing this). If you experience any odd problems with your Synergy that are not configuration bugs, try using Synergy+ instead. My configuration of Synergy is slightly more complex than your average one. The main differences are that the top and bottom 5% of each screen are not shared, so you can safely use the buttons and window-controls in each corner without problems of jumping to adjoining screens. Also, I have a Logitech Revolution MX mouse, which has about 9 buttons. I have added mouse button confi...