Free performance monitoring for VMware™ and IBM Power Systems™

How can LPAR2RRD help you in migration planning?

LPAR2RRD can be found very useful in migration or new deployment planning. If there is going to be deployed or migrated an application which is already running somewhere and LPAR2RRD has its performance data then there can be easily predicted CPU load on the new HW.
This will help you in accurate sizing of a new HW before purchasing it!

Lets demonstrate this ability on following 2 examples by usage of LPAR2RRD CPU Workload Estimator

Scenario 1 - migration to new HW

  • new target server: IBM Power 710, 4 x 3GHz
    you can select any server from pre-defined ones (complete IBM Power Systems™ product line)
  • LPARs to be migrated:
    • server ASRV12 (IBM Power 750, 16 x 3Ghz), LPARS:
      • ASRV12LPAR4
    • server BSRV21 (IBM Power 750, 16 x 3Ghz), LPARS:
      • BSRV21LPAR19
      • BSRV21LPAR7
    • server BSRV22 (IBM Power 750, 16 x 3Ghz), LPARS:
      • BSRV22LPAR10
      • BSRV22LPAR13
      • BSRV22LPAR16
      • BSRV22LPAR22
The graph shows aggregated CPU load of all migrated LPARs in rPerf benchmark for period of 1 week since 5th Dec.
You can see there in bold black line max CPU capacity of the target server in rPerf benchmark.
As per the graph is clear that the new target HW (p710) will not cope with all CPU peeks!!
There should be considered another more powerful server.
CPU Workload Estimator - new HW

Scenario 2 - migration to already existing HW

Only the difference is that the target HW already exists and is utilized somehow. Then CPU load of migrated LPARs has to be added to already existing CPU load.
  • already existing server : ASRV11 (IBM Power 750, 16 x 3GHz, default pool)
  • LPARs to be migrated:
    • server ASRV12 (IBM Power 750, 16 x 3Ghz), LPARS:
      • ASRV12LPAR4
    • server BSRV21 (IBM Power 750, 16 x 3Ghz), LPARS:
      • BSRV21LPAR19
      • BSRV21LPAR7
    • server BSRV22 (IBM Power 750, 16 x 3Ghz), LPARS:
      • BSRV22LPAR10
      • BSRV22LPAR13
      • BSRV22LPAR16
      • BSRV22LPAR22
The graph shows again aggregation of all migrated LPARs together with existing CPU load on the target server (red area, 10.6 rPerfs) in rPerf benchmark for period of 1 week since 5th Dec.
You can see there in bold black line max CPU capacity of the target server in rPerf benchmark.
As per the graph is clear that the target server will easily cope all new CPU workload.
CPU Workload Estimator - existing HW
Note that as a target you can select whatever CPU pool on whatever server in your environment.

Form snapshots

Here are snapshots of both scenarios after LPAR/server selection and before generating graphs(picture details on a click):
1st scenario2nd scenario
CPU Workload Estimator scenario 1 CPU Workload Estimator scenario 2

Note

Both above scenarios are based on rPerf benchmark which is one of benefits full LPAR2RRD distribution.
Free LPAR2RRD distribution has same ability but based only on CPU cores comparison (it is useful for cases where you migrate between same kind of servers)
You can test both scenarios on live demo