>No Im saying in the specific case that you really need accurate response >times and the architecture is like yours , you might need to do this. >Again there are so many factors that influence a page load time as a browser >sees that it is not usually worth doing any exhaustive testing for this.
So the bottom line is that in order to calculate a page loading time using JMeter, a tester needs to find out the proportion using different set ups and then use that proportion to interpret the test data. Correct? >(And page load time is just one part of a family of load testing) What else would you suggest to test on a static pages (no dynamically generated stuff)? >In some of your original screens the times for the same static file varied >from a few ms to a few seconds. Thats not uniformly slow. If your Server was >loaded , then it should be simple to find this out using perfmon If response time for all resources increase with the same proportion, it is uniformly. >Yes but you get a java stack trace that may have some more information or >lets you look into JMeter source and see what it was trying to do. What is a JMeter source? Is it another log file? -- View this message in context: http://jmeter.512774.n5.nabble.com/Test-plan-for-970-page-requests-every-5-min-tp2826174p2847080.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
