DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42506>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42506 Summary: JMeter threads all use the same SSL session Product: JMeter Version: 2.2 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: HTTP AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When issuing HTTPS requests, JMeter threads all use the same SSL session. This prevents JMeter from testing real-world performance of SSL sites. (One can look at SSL session IDs in the Apache httpd custom access log with %{SSL_SESSION_ID}x format specifier). This means that JMeter only does the SSL handshake once with the server in the beginning of the test, not at the beginning of each thread. The handshake is the expensive part of SSL protocol, and bypassing it can seriously skew the performance figures. I've done measurements with other tools that do SSL handshake properly, and in some cases the performance difference is 4-fold. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
