Hi, do not use the "keep-alive" option on samplers, as https connexions are not reused anyway... It can tilt your connection stack (and do not know what else on Linux...). How many threads do you use ? Each sampler is going through the whole ssl connexion process each time (not reused), so the more images, css, js files you have, the less your response time means smthg... Check the logs on your ssl box too...
Cheers, Laurent -----Message d'origine----- De : Tuomo Pyh�l� [mailto:[EMAIL PROTECTED] Envoy� : lundi, 24. novembre 2003 17:26 � : [EMAIL PROTECTED] Objet : Initial problems when using jmeter Hi, I tried jmeter and for me it seems to be somewhat slow. I tried running it on 1.3GHz PC (Running RH Linux 9.0, JDK 1.4.2) , and I was able to get throughput ~100req/min. For me this seems to be quite small amount of requests! The machine running jmeter seems to be running out of cpu (cpu usage ~100%). The machine running the server had a plenty of idle cpu power. I wonder, what might be the reason for the behavior? I tried running jmeter on other machines also (different OS), and observed similar behavior. The test plan included some https-requests, cookie-manager and authentication manager. I checked the requests to retrieve the images also and added some assertions. I think ~100req/s excludes retrieved images but still, it is a low amount of requests as the pages have maybe 5 images or so per page. What should I do to improve the performance? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
