1. What version of LoadRunner (LR) or PerformanceCenter (PC) are you using? (specify which tool LR or PC)
2. What is the protocol you are recording?
2.1 If .NET, which version of .NET does the app require?
2.2 If .NET, which version of .NET do you have installed?
2.3 If OracleNCA with Oracle Forms Server, please list the version of Oracle Forms Server. You can get this info from the main Oracle Form when launched - Help -> About
3. If HTML - are you using HTML-Advanced with URLs or,
4. If URL mode:
- Concurrent groups, or
- Without Concurrent groups?
5. Which LoadRunner/PerformanceCenter feature (FPs) or service packs are you using?
6. VuGen Recording - are you using Old or New Recording Engine?
7. You must list here the specific Licensed Vuser type for your specific issue AND the license amount you have for your Vuser protocol(s) - per the example below (Unlimited, Permanent, N/A, etc. are not options) .
8. Is your support/maintenance contract current and active?
9. What platform(s) (PCs) and Operating Systems (Windows-XP, etc.) are being used for load generators and controllers? Include version and service packs (SP1 or 2, etc.)
Win XP SP 3
10. If you have filed a service request with HP/Mercury, what have they told you at this point with respect to your issue?
Yet to file.
Load tested the first release of an application with 20 scripts and with the runtime setting "Check for newer version of stored page..." enabled. Average hits/sec was observed in the range 40 to 45.
Load tested the next release (No hardware change or major functionality changes) with same scripts and same scenario but with the runtime setting "Check for newer version of stored page..." disabled. Average hits/sec was observed in the range 15 to 20.
Also the response times were low comparatively. The development team confirmed that they did not do any major changes or tunings which may impact performance. Will the above mentioned run time setting make any difference?
If yes what is the best practise? Enabling or disabling?
Re: Runtime Setting - Check for newer version of ...
By making the change to enabled you have defeated the client side caching mechanism resulting in a higher request rate than would be the norm. This would naturally result in an increase in the number of requests, with the increase coming from those pages which would have been resident unexpired in cache.