Loadrunner Environment: Performance Centre 11
Protocol : RTE
Injector: Windows 2008 R2 Servers with 16 GB RAM.
Script: The functionality in the script only navigates to 4 - 5 screens and is therefore lightweight.
I am currently doing a PoC to identify how many RTE users should be run from one injector. When I ran 50 RTE users from an injector, the CPU and Memory utilisation was minimal - memory usage was around 50Mb for the mdrv.exe process throughout the duration of the run. Having read some information on web, there are mixed reviews - some suggesting not to run more than 50 RTE from an injector whereas some suggesting to run upto max of 150 vusers. As I understand, the main thing to monitor while running these RTE users is to monitor GDI handles which I did. I ran a single user test from vugen and task manager reported maximum of 85 GDI objects being created under the mdrv.exe process. Interestingly, when I ran a 50 user test from an injector, the task manager on the injector reported zero GDI objects.
We are currently only licenced with 50 RTE users which will be extended to 300 RTE licences in next couple of weeks or so. Once we have these extra ones, I am planning to ramp up more users to identify the magical figure.
The eventual test we want to run is with 300 concurrent RTE users and with the current recommendation of 50 per injector means that we will need more injectors which will cost and this exercise is to prove whether it is really necessary and can be handled with 2-3 injectors which are already in place.
Can anyone please share any experience or shed some light?
As far as I know, RTE though seems as if it is working at the application level, it is still working at the transport level reading the telnet/ssh traffic and finding the row/column values of the corresponding text (text processing). So, I'm not sure if it would really use that many GDI objects. May be - my understanding is wrong. I've successfully tested 150 RTE users on a system with 8GB RAM and 2CPU cores. Again, your case might be different. I would be only worried if I'm testing a protocol like Citrix/RDP/SAP GUI to go this far to evaluate the h/w requirements.
The views expressed in this forum are mine. My organization does not subscribe to the substance, veracity or truthfulness of the said opinion