Having a larger memory and CPU footprint for test configured to download embedded resources is expected as in the majority of cases main request is relatively small being compared to embedded resources size.
1. Make sure you're following JMeter Best Practices <http://jmeter.apache.org/usermanual/best-practices.html> 2. Make sure you're using the latest version of JMeter 3. Make sure you have HTTP Cache Manager <https://www.blazemeter.com/blog/using-http-cache-manager> added to your Test Plan. This bit is vital as real browsers download embedded resources found in the web pages (images, scripts, styles, fonts, etc.), but they do it *only once*, on subsequent requests these embedded resources are being returned from the browser's memory and/or disk cache. So having HTTP Cache Manager is a must for properly simulating real users, otherwise you will be conducting too much load therefore your test results won't be accurate. -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
