My Top Five Issues with Performance Center

I previously discussed what I saw as the main advantages to HP Performance Center, however I also have a number of grips using the software. What follows are the top five areas I which I think Performance Center could be improved upon:

  1. The Performance Center User administration user interface relies intensively on AJAX calls, e.g. for every mouse click the page is rendered context-sensitively. This results in numerous AJAX requests to redraw practically every piece of the UI (buttons, fields, menu items, etc.). This isn’t too much of a issue if you are on the same LAN as Performance Center, however it becomes slow and unresponsive if you are working over a WAN and VPN.
  2. Open dialogs will list items in an arbitrary order. This may seems to be a minor irritation, however if your performance project contains more than 20 scripts you spend more time than you should locating them. The same applies to the Analysis’ open dialog where you struggle to locate the right test result. A lexicographical ordering would help here a lot. Also, earlier Performance Center versions do not support version control. This means you have to include version control naming conventions in your scripts – this also results in more versions of the script name.
  3. HP recently reorganized the website structure of the product range, including the Loadrunner forum pages. However they have not migrated the URL structure, this means if you use a search engine to find a specific topic, or have saved bookmarks, you will not be directed to the correct page.
  4. There are some nice new features, which do not appear to working comprehensively. I particularly would like to see the web protocol’s “AJAX Click and Script” functioning correctly. This script type aims to emulate JavaScript behavior. AJAX is now a common approach in web 2.0 applications, just think about field validation use-cases or asynchronous display of results, etc. In terms of performance testing it means that the VuGen records user actions (e.g. field edits, image map clicks, etc.) and plays back the respective AJAX HTTP requests accordingly, without having to script those requests individually. The major benefit (would be) to save time and effort parameterizing and correlating the JavaScript calls. However, this script type supports only a few JavaScript frameworks. For example, if the application under test uses jQuery then you will receive JavaScript and validation errors during playback.
  5. Lack of runtime configuration of scripts. Within Loadrunner you are able to define configuration parameters (“Additional Attributes”) and Parameter Lists in the Virtual User Generator. However there is no way to change them in Performance Center when configuring your individual test execution. There are some instances when you are required to repurpose scripts, this means a making a copy of the script is the easiest route in order to change the configuration and parameter list. This also in turn increases the number of scripts and adds to the complexity of housekeeping.

Overall I am happy with Performance Center and it gives me the ability to get the job done. However the usability of the web-interface can be frustrating.

3 thoughts on “My Top Five Issues with Performance Center

  1. Another problem that I found in Performance Center you cannot add another script in the middle of scenario execution. It seams that PC allow you to do so but all vusers are failing.

    1. Yes, I agree.
      One possible workaround is to include your common files from a shared network directory, something like:

      #include "\yourfileserver.yourdomain.netyourscriptsscript.c"

      Can be an acceptable solution, if you do not change your scripts much…

  2. Hi,

    When we select auto run in PC11 to auto start a test at 9am wich is set in PC at 8pm time. Later when we go back to PC11 at 9.10, can we view the current running test in PC11 ?

    Please advice if we can view if so with what path of the project login.


Leave a Reply

Your email address will not be published. Required fields are marked *