Tomcat Performance Tuning Jumping Bean（Tomcat性能调优跳豆）.pdfVIP

Tomcat Performance Tuning Overview ●Tomcat Architecture ●What are Tomcat Connectors? ● HTTP KeepAlive ● Apache HTTP + Tomcat ●Load Balancing/Clustering Options ●Logging ●Thread Executors ●Caching ●Tuning JVM 80% of HTTP request round trip time is spent in application Tomcat Architecture Tomcat Connectors - HTTP ● HTTP Connector – 8080 – Coyote ● Server Shutdown – 8005 (not a connector) ● Connector protocol attribute: – HTTP/1.1 ● Direct access to Tomcat for HTTP requests Tomcat Connectors - AJP ● AJP Connector – 8009 – ”Client” Connectors – Apache mod_proxy, mod_jk2 ● Connector protocol attribute: – AJP1.3 ● Configure in Apache httpd.conf – mod_proxy, – mod_ajp Tomcat Connectors 2 ● Different connectors – Native APR library - AprLifecycleListener, – BIO – Blocking Java connecotr (default), – NIO – Non blocking Java connector Tomcat Connectors 3 ● BIO use when: – Stablity is important, – Keep alive not a limiting factor, – Content is dynamic, ● APR – use when: (Almost always) – faster, especially for SSL, not an issue if using SSL on Apache http, – Lots of static content (sendfile) HTTP KeepAlive HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using the same TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/re