IBM’s Relative Performance (rPerf) metric is a great tool for comparing commercial workload performance between different Power System servers. It’s often. This post outlines a recent Nigel Griffiths tweet about estimating rperf for your LPAR. Read on to find out more. Articles on IBM AIX performance including server throughput, system performance and IBM AIX commands.
|Published (Last):||9 November 2005|
|PDF File Size:||11.17 Mb|
|ePub File Size:||12.49 Mb|
|Price:||Free* [*Free Regsitration Required]|
So lets talk about things you should think about when using rPerf to make sizing or performance estimates.
There is an excellent article in a recent IBM Systems Magazine on exactly this subject and I refer you to that rather than duplicate it here.
Benchmarks are popular because they have measurable and repeatable performance objectives and workloads. Read The Current Issue: If you are some where between these options then you may have to make aaix series of changes, upgrades or updates to achieve good performance on your new machine. Actual performance will vary, based on application and configuration details. This is especially important for older, single threaded applications that cannot exploit the benefits of SMT.
This is normal tuning like disk queue depth, memory use, large network packets. The pSeries is the baseline reference system and has a value of 1. Rpperf, there are times when this approach isn’t possible. rperg
No Network Issues – as above. Having stated that, many people use rPerfs as a simplistic way of preparing a gperf to planning new machines based on running POWER workloads for both workload migration and server consolidation. The main reason was to publish data for a broad selection of Power Systems servers. For workload migrations and server consolidation projects, rPerf data is frequently used for CPU sizing. Provide a reason for quarantining this blog entry optional: The script will give a lower than actual rPerf number.
Running older software from the older machines can cause a mismatch with your rPerf expectation.
Simply stated, benchmarking refers to running a set of programs on various computer and network configurations and measuring the results. These requirements would make it extremely costly to publish multiple data points for each Power Systems model.
Particularly, take and early opportunity to apply the first two updates after the initial rperff. Performance tuning is always an iterative process of removing one performance bottleneck in order to reveal the next performance bottleneck. Running industry benchmarks can be very expensive. Numerous benchmark programs are in use today.
IBM Systems Magazine – AIXchange blog
Particularly as you move to larger servers, the topology of the cores and memory that are used can have a big effect on the cache and memory roerf of the LPAR and thus have a big effect on the actual performance.
Achieving a Resilient Data Center Implement these techniques to improve data-center resiliency. If you are break just one or two and then only a little bit then you never know – “you might get lucky”.
Instead, the analyst has decided to use standard benchmark results to size the new hardware. Additionally, the actually real world performance of a given server might be affected over time prerf improvements or bugs in the firmware, AIX, or the application while the official rPerf is seldom changed in the Power Systems Performance Report after the initial release of the server model.
Also no SAN bottlenecks.
Continue to Wikis
He can be rperff through www. How will the script get updated? IBM is currently completely out of “magic pixie dust” to fix problems without changes. The biggest pitfall is trying to use benchmarks without knowing the system bottleneck.