One of the most appealing features of HP Performance Center is the automatic resource management. The Performance Center infrastructure can be shared between multiple test projects. Each project bundles the test scripts, test data and the associated load test configurations. Several load generators (aka. hosts) can be assigned to a Performance Test Project. From the tester’s perspective the Performance Center supervises which load generators are dedicated to a certain test type and ensures that load generators (as precious resources) are shared between projects.
In HP Performance Center Admin Site User Interface load generators can be grouped, and placed into resource pools. Assigning these pools to performance projects governs which project has access to which load generators.
Load Generator hosts can be either equivalent or different. Technical properties (machine type, hardware, installed software, network capabilities), geographical location and planned use can vary the scheme.
To differentiate test projects to this respect, different host pools are to be defined. It is a good practise to place non-equivalent Load Generators into different pools.
However only one host pool can be assigned to a project. To establish better flexibility and host utilization, merged pools can be defined. This is a union of several resource pools, which means, the assigned projects are allowed to use the any load generators of the contained host trackback lascia un commento capsiplex in usa pools.
In the example below we have 3 basic resource pools, General, Budapest and Vienna. Then we defined Austro-Hungary to union the pools Budapest and Vienna.
Below, the merged pool is getting assigned to the performance project:
During testing a Load Generator may be compromised. A faulty hardware or inability to access certain network segments are good examples for these. In this case the Host can be taken out of rotation by setting the host status to maintenance. Doing so will not affect the resource pool definition, it simply tells Performance Center not to pick that host for test execution.
By default Load Generators are selected automatically based on availability by the Performance Center. This default behaviour is appropriate and comfortable for most of the cases. If a specific Load Generator Host is needed for a test (and no changes in the pool definition is desired), the selection strategy can be overridden.
Below I changed the strategy to “Assign actual load generators to groups”. This makes it possible to select exactly which physical load generators should execute the load test. (Note: more than one load generators can be assigned to a load test, which extends the load capacity of your tests.) After selecting this option on the testgroup configuration pane you can make the necessary assignments to fit the testing needs.