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):||21 April 2016|
|PDF File Size:||9.82 Mb|
|ePub File Size:||11.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
This is normal tuning like disk queue depth, memory use, large network packets.
Read The Current Issue: 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 affinity of the LPAR and thus have a big effect on the actual performance. Note, although rPerf may be used to compare estimated IBM UNIX commercial processing performance, actual system performance may vary and is dependent upon many factors, including system hardware configuration, software design, and configuration.
Read The Current Issue: Performance tuning is always an iterative process of removing one performance bottleneck in order to reveal the next performance bottleneck. This is especially important for older, single threaded applications that cannot exploit the benefits of SMT.
The rPerf Benchmark
He can be reached at ccler forsythe. We’ll focus on the rPerf benchmark, which is an estimate of commercial processing performance, relative to other pSeries systems, used by IBM. These rperc would make it extremely costly to publish multiple data points for each Power Systems model. Numerous benchmark programs are in use today. No Network Issues – as above.
Sizing with rPerf but Don’t Forget the Assumptions (AIXpert Blog)
There is prerf excellent article in a recent IBM Systems Magazine on exactly this subject and I refer you to that rather than duplicate it here. But I hope this blog entry will help every one to either get it right first time or at least set realistic expectation and outline some prime areas that rpedf need investigation to realise benefits, thanks Nigel Tags: Implement these techniques to improve data-center resiliency.
Having stated that, many people use rPerfs as a simplistic way of preparing a guesstimate to planning new machines based on running POWER workloads for both workload migration and server consolidation. These guidelines may help you achieve the performance that you expected.
Charlie Cler supports customers in a solutions-architect role at Forsythe Technology Aic.
The most exciting POWER6 enhancement, live partition mobility, allows one to migrate a running LPAR to another physical box and is designed to move running partitions from one POWER6 processor-based server to another without any application downtime whatsoever. Simply stated, benchmarking refers to running a set of programs on various computer and network configurations and measuring the results. There are many pitfalls in using benchmarks in computer sizing endeavors.
Specifically, a computer benchmark is a computer program that performs a strictly defined workload set of operations and returns some form of measurable result i. Firmware is Current – The firmware includes xix Hypervisor and this has many performance enhancement tweaks and often based on field experience that you need working for you.
The tuning setting from older machines and OS are unlikely to work perfectly. For example, suppose that a company has plans to roll out a new Web-based ordering system. Note that rPerf can only be used for making comparisons within Power servers. Running older software from the older machines can cause a mismatch with your rPerf expectation. In this case, the script guesses the rPerf based on rPerf numbers in a fairly crude way.
This is because the doubling of transactions may be based on doubling the number of threads of work rather than doubling the speed of each thread. However, there are times when this approach isn’t possible.