hi, this would be a complex answer.
- As you may know, the EXTRARES means, EXTRA Resources. When client application send the first request, server send the main frame back. However, resources like images, applets, CSS files, Javascript, are commonly found in different locations. So, each of them needs an additional GET call to download those resources. Each of those GET are an EXTRARES line. Said this, we are user see just one call, while the application can make as much calls as resources needs to download.
- Recording EXTRARES or not recording doens't mean, download or not download those EXTRARES during replay. This just change the way as we see the script.
- What is the best practice? We don't have best practice. This depends on how your application and environment behaves. So that, you can make the script to behave similar to the real browser or application through Run- Time Settings. For example:
1. * What is the browser used in your environment? or the browser used by the users that access the application?
- This can be changed in Run-Time Settings--Browser Emulation. Changing the browser change how the Caché memory is handled, number of concurrent connections, cookies and headers. So, this may affect.
2. * Do the users access the application frequently and have rights to save temp files during the navigation? I
- If so, that means the extra resources are saved in temp files for the browser and they are not downloaded again after the first time. So, downloading the page will be faster. In this case, we can change settings like:
/ Simulate Browser Cache
/ Download non-HTML Resources
/ Simulate a new user on each iteration - Clear cache on each iteration.
3. * Emulate the proper Network Spped in Run-Time Settings--Network-- Speed Simulation
Finally, consider that LoadRunner reports the transaction time from the moment in which client sends the request until the moment in which the last buffer was received from the server. Depending on the application, and of course, the browser, there is an additional time for rendering the page. So, this is client side and is not related to server response. So, we as users can see the application is taking more time than Vugen (commonly).
I hope this helps. Please let me know if you have more questions.