As HxGN EAM Extended is a web-based product, a lot of parameters affect client performance. Parameters like Bandwidth, latency, application server and database hardware, client processing power, client memory, system usage and time the server has been running all contribute to the performance metrics.
This section gives details about the performance results collected during the test on a LAN bandwidth with 2 ms latency over a period of the 168 hrs. For details about results on other bandwidth / latency combination please refer to the Bandwidth / Latency charts section at the end of the document.
A 2x2.60 Ghz, 32 GB RAM virtual machine was used while performing the tests.
The LoadRunner tool uses HTTP posts to simulate users. Although transaction response times can be captured with LoadRunner the use of HTTP posts excludes the execution of any client processing (e.g. java scripts). To accurately capture client side application response times that include client processing a separate automation script was developed that completes selected application activities (e.g. screen and tab opens) by executing the HxGN EAM Extended application user interface and recording the times following completion of each event (e.g. screen open)
The chart below gives overviews of the average screen open times and average save transaction times over a period of 168 Hrs.
The next chart below gives timings of various screen open transaction over a period of 168 Hrs.
And the final chart below gives an overview of the Save Transaction over a period of 168 Hrs.