Re: Tomcat7 HTTPS APR Performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shivani, On 7/19/2010 2:02 PM, shivanic wrote: > I would recheck the performance stats with 100 users with HTTP protocol > instead of HTTPS and revert back. Mladen Turk has mentioned that only > constant response time (and not allowing the factors that make it vary like > access to external resources) - can determine the absolute picture of the > container behavior. I agree on that point - however as you can see the > differences are huge - specifically the average response time wrt op like > login to application. Login involves a simple ldap bind and the test case > involves only login with correct pwd. Still, you ought to be able to login faster than even 38 seconds on average if all you're doing is a simple LDAP authentication. Yes, Tomcat7 appears to take ~3x as long, but your baseline time still stinks. Perhaps you have a hideous misconfiguration somewhere? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxEw6YACgkQ9CaO5/Lv0PDgqgCgj8Q0jNbxpMPLmX/Zqg5nY/py yEsAniVn/6oya0vVGqaGM/ezmXbjdXsX =ShZX -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 HTTPS APR Performance
Christopher Schultz-2 wrote: > > > Can you clarify? Are you using the same version of APR with both Tomcat > 7 and JBoss? APR 2.1.4 is an unlikely version number. Care to > double-check? > Correction : It is jboss web server version 2.1.4 used. APR Version used is the latest available 1.4.2 Both Jboss Web Server and Tomcat7 are enabled with APR and using JDK6. >> While doing load testing with HP Load Runner we observed the following >> response times(seconds) for 100 concurrent users: >> Tomcat7 JbossWebServer-2.1.4Jboss4.2.3 >> >> Login 94.63 38.74 63.826 > > > Wow... login takes 30 second under the best of conditions? That seems... > long. Or, is this the total time to serve 100 requests all at once? > It is the average response time of the application when under a load of 100 concurrent users. For login - authentication is being done from LDAP Server. > Uhh... there could be many reasons that your webapp runs slowly. > I would recheck the performance stats with 100 users with HTTP protocol instead of HTTPS and revert back. Mladen Turk has mentioned that only constant response time (and not allowing the factors that make it vary like access to external resources) - can determine the absolute picture of the container behavior. I agree on that point - however as you can see the differences are huge - specifically the average response time wrt op like login to application. Login involves a simple ldap bind and the test case involves only login with correct pwd. > http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Request_Dumper_Filter > Note that you will configure this component in web.xml, now, and not in > context.xml. > Chris, thanks for this info!. Shivani -- View this message in context: http://old.nabble.com/Tomcat7-HTTPS-APR-Performance-tp29180708p29207557.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 HTTPS APR Performance
On 07/16/2010 09:08 AM, shivanic wrote: Hello, For comparing performance of Apache Tomcat 7 with APR and Jboss Web Server with APR version 2.1.4 with Tomcat 7 we have done a load test of an app. Your results only show that you have used load testing wrongly. Hitting the server with the simple DoS tool won't give you any relevant relevant info unless you are hitting the web application that has constant response timeout (a bit oxymoron). Such web applications are for example Default servlet, which won't also give you the correct results, cause depending on the file size APR might choose to serve that via OS sendfile, in which case OS might cache that resource and give you the faulty sense of speed. Also the JVM might have it's own logic for GC (easily observable by multiple runs) However if your web application access the external resource (database or something) that has variable response time, all you get as result of testing is the state of that resource availability at the time test was run, not the performance characteristics of the application server. Just to prove my point, use your current test for any of the application servers you've tested so far, and repeat the same test with some random time between test runs, then do the same thing each time restarting the app server, and cleaning up the log files, and you'll see that numbers simply make no sense :) Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 HTTPS APR Performance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shivani,
On 7/16/2010 3:08 AM, shivanic wrote:
> For comparing performance of Apache Tomcat 7 with APR and Jboss Web
> Server with APR version 2.1.4 with Tomcat 7 we have done a load test
> of an app. The Open SSL and APR libtcnative files were in the path
> using the LD_LIBRARY_PATH env variable. The protocol used was HTTPS.
Can you clarify? Are you using the same version of APR with both Tomcat
7 and JBoss? APR 2.1.4 is an unlikely version number. Care to double-check?
> While doing load testing with HP Load Runner we observed the following
> response times(seconds) for 100 concurrent users:
> Tomcat7 JbossWebServer-2.1.4Jboss4.2.3
>
> Login 94.63 38.74 63.826
Wow... login takes 30 second under the best of conditions? That seems...
long. Or, is this the total time to serve 100 requests all at once?
> Tomcat7 has the following server.xml configuration :
>
> maxThreads="350" scheme="https" secure="true"
>clientAuth="false" sslProtocol="TLS"
> SSLCertificateFile="${catalina.base}/conf/server.crt"
> SSLCertificateKeyFile="${catalina.base}/conf/server.key" />
>
> As you see, the attributes "acceptCount" and "connectionTimeout" are not
> specified. How much impact can these have on the response time of Apache
> Tomcat 7?.
I can't imagine that these timeouts would be diminishing your
performance. About all you might be able to do is refuse connections
more quickly, but that's unlikely to be your goal.
> What all the are the ways in which we can determine the cause of
> the high response time for Tomcat?
Uhh... there could be many reasons that your webapp runs slowly.
> Also I noticed that RequestDumper Valve can no longer be used in Tomcat7.
> Any specific reason why this has been removed - is there any alternative
> debugging valve created? Since that is frequently used to debug the response
> headers.
RequestDumperValve has been replaced by RequestDumperFilter, part of an
effort to replace Valves with Filters to be more spec-compliant, and
therefore more flexible. This is the class you want:
org.apache.catalina.filters.RequestDumperFilter
Also see:
http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Request_Dumper_Filter
Note that you will configure this component in web.xml, now, and not in
context.xml.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxAuC0ACgkQ9CaO5/Lv0PBnfACdEiqZGj4v0AjEz+E6M9Of7brX
vQQAoJa10JfbnXmZBVq9wClIsUfJYzUt
=gbDN
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 HTTPS APR Performance
The JDK Versions used for each are as follows: Tomcat7 - JDK 6 / APR enabled / Open SSL JbossWebServer - JDK 6 / APR enabled / Open SSL Jboss4.2.3- JDK 5 / No APR / JSSE - Regards -- View this message in context: http://old.nabble.com/Tomcat7-HTTPS-APR-Performance-tp29180708p29180788.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat7 HTTPS APR Performance
Hello, For comparing performance of Apache Tomcat 7 with APR and Jboss Web Server with APR version 2.1.4 with Tomcat 7 we have done a load test of an app. The Open SSL and APR libtcnative files were in the path using the LD_LIBRARY_PATH env variable. The protocol used was HTTPS. While doing load testing with HP Load Runner we observed the following response times(seconds) for 100 concurrent users: Tomcat7 JbossWebServer-2.1.4Jboss4.2.3 Login 94.63 38.74 63.826 Prj Select57.15 23.835 7.753 SaveData 29.665 2.677 1.681 PageRender 15.071 2.659 12.456 Logout0.092 1.9730.089 For 50 concurrent users the following were the response times(seconds) Tomcat7 JbossWebServer-2.1.4 Jboss 4.2.3 == Login 17.469 20.767 15.633 Prj Select 1.9429.212 3.431 SaveData 1.2091.663 2.222 PageRender 1.2074.447 2.091 Logout 0.1920.326 0.29 Tomcat7 has the following server.xml configuration : As you see, the attributes "acceptCount" and "connectionTimeout" are not specified. How much impact can these have on the response time of Apache Tomcat 7?. What all the are the ways in which we can determine the cause of the high response time for Tomcat? The catalina.sh has the following JAVA_OPTS -Xms128m -Xmx768m -XX:MaxPermSize=512m Also I noticed that RequestDumper Valve can no longer be used in Tomcat7. Any specific reason why this has been removed - is there any alternative debugging valve created? Since that is frequently used to debug the response headers. Thanks, Shivani -- View this message in context: http://old.nabble.com/Tomcat7-HTTPS-APR-Performance-tp29180708p29180708.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
