JavaPerformanceChapter_10
0 likes11 views
This document discusses strategies for improving web application performance in Java. It covers monitoring and tuning web containers, including optimizing thread pool parameters, connection queues, and request handling. The document also provides best practices for Java servlets, JSPs, caching content, managing sessions, leveraging HTTP server file caches, and analyzing access logs to enhance performance.
JavaPerformanceChapter_10
- 1. Java Performance Chapter 10 1 Saurav Basu 6/3/2020
- 2. Organization 1. Strategies, Approaches, and Methodologies 2. Operating System Performance Monitoring 3. JVM Overview 4. JVM Performance Monitoring 5. Java Application Profiling 6. Java Application Profiling - Tips & Tricks 7. Tuning the JVM - Step by Step 8. Benchmarking Java Applications 9. Benchmarking Multitiered Applications 10. Web Application Performance 11. Web Services Performance 12. Java Persistence & Enterprise Java Beans Performance 2
- 3. Web Application Performance 3 1. Web Container Architecture 2. Web Container Monitoring & Perf 3. Best Practices
- 4. Web Application Performance 4 1. Web Container Architecture 2. Web Container Monitoring & Perf 3. Best Practices
- 5. Web Application Performance 5 Web Container Architecture
- 6. Web Application Performance 6 1. Web Container Architecture 2. Web Container Monitoring & Perf 3. Best Practices
- 7. Web Application Performance 7 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 8. Web Application Performance 8 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 9. Web Application Performance 9 Web Container Monitoring ThreadPool Parameters
- 10. Web Application Performance 10 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 11. Web Application Performance 11 Web Container Monitoring Connection Queue Parameters
- 12. Web Application Performance 12 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 13. Web Application Performance 13 Web Container Monitoring Keep Alive Parameters
- 14. Web Application Performance 14 Web Container Monitoring Keep Alive Parameters
- 15. Web Application Performance 15 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 16. Web Application Performance 16 Web Container Monitoring Request Parameters
- 17. Web Application Performance 17 Web Container Monitoring 1. ThreadPool Parameters 2. Connection Queue Parameters 3. Keep Alive Tuning 4. Request Parameters 5. Custom MBean
- 18. Web Application Performance 18 Web Container Monitoring Custom MBean
- 19. Web Application Performance 19 1. Web Container Architecture 2. Web Container Monitoring & Perf 3. Best Practices
- 20. Web Application Performance 20 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 21. Web Application Performance 21 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 22. Web Application Performance 22 Best Practices Servlet and JSP Init and ContextListener for Caching Include directive vs Include Action Trim Whitespaces Jsp:UseBean ExpressionLanguage
- 23. Web Application Performance 23 Best Practices Servlet and JSP
- 24. Web Application Performance 24 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 25. Web Application Performance 25 Best Practices Content Caching
- 26. Web Application Performance 26 Best Practices Content Caching
- 27. Web Application Performance 27 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 28. Web Application Performance 28 Best Practices Session Persistence Load Balancer useruseruseruseruser Session Store Serialize/Deserialize App Server App Server App Server
- 29. Web Application Performance 29 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 30. Web Application Performance 30 Best Practices Http Server File Cache
- 31. Web Application Performance 31 Best Practices 1. Servlet and JSP 2. Content Caching 3. Session Persistence 4. Http Server File Cache 5. Access Logs
- 32. Web Application Performance 32 Best Practices Access Logs
Editor's Notes
- #3: Next we look at the topic of Web application performance
- #4: Under Web application performance we will discuss Web Container architecture, Monitoring and Performance and Best practices related to Application Servers
- #5: First we will talk about web container architecture
- #6: This slide depicts the architecture of webcontaine The server consists of one or more connectors that share a single engine component. The engine in turn contains one or more virtual hosts each with one or more applications (Context). Within each application are Java Servlets and JSPs
- #7: Next we will talk about Web Container Monitoring
- #8: This slide list the key areas of monitoring of web applications namely ThreadPool, ConnectionQueue, KeepAlive and Request parameters and lastly custom mbean
- #9: Let first talk about threadpool parameters
- #10: This slide depicts the 2 important thead pool metric to monitor namely the max threads count and the currentthreadsbusy-count, if the value of currentthreadbusy count is consistently equal to maxthreads count and there is spare cpu resources consider increasing the threads count however excessively high value can be detrimental due incurred context switch and cache miss
- #11: Next we will talk about Connection Queue parameters
- #12: This slide shows the most important conncection queue parameter to monitor is the countoverflows-count. Increasing queue size reduces overflows at the expense of higher response times for the client or to scale vertically or horizontally,
- #13: Next we will talk about parameters related to keep alive setting on the application server
- #14: This slide shows the most important keep alive parameters to monitor. The high valuue of count-hits count indicates current settings are working well.
- #15: This slide depicts the use of the asadmin command to fetch the value of the keep alive parameters
- #16: Next we will talk about request parameter monitoring
- #17: This slide highlights the important request parameters for the purpose of monitoring of the application server
- #18: Next we will talk about Custom mbean for performance monitoring
- #19: This slide shows a sample mbean for monitoring application specific statistics (ex standard deviation ) as shown in this example.
- #20: Next we will talk about Best practices for improving the performance of web applications
- #21: We will discuss the best practices for the following areas Servlet and JSP Content Caching Session Persistence Http Server File Cache Access Logs
- #22: First we will talk about best practices for Servlet and JSP performance
- #23: In this slide we talk about best practices for optimal performance of servlet and jsp pages. Use of init and contextlistener for caching Use of jsp include diective for static pages while include action for pages with dynamic content Use of trimwhitespace option in the config file to reduce network packet sizes Use of beanname instead of classname makes bean instantiation costlier
- #24: This slide shows an example of bean instantiation cost incurred when using bean name attribute
- #25: Next we will talk about best practices for Content Caching
- #26: Content Caching on the serverside can improve performance of static file that donot change frequently. These can further be compressed to reduce network latency in transmission This slide shows an example of compression and uncompression that takes place prior to serving resource from from cache.
- #27: This slide shows the impact of different compression schemes on transaction throughput
- #28: Next we will talk about Session Persistence
- #29: This slide depicts the use of external session store to ensure resumption of session after server failure
- #30: Next we will talk about http server file cache
- #31: File caching can improve performance by eliminating the disk I/O associated with the reading of a file for every request in the absence of the cache. This slide shows the list of parameters to monitor for filecaching in glassfish.
- #32: Next we will talk about http access logs
- #33: Access Logs can help identify identify poorly performing request paths, understand application usage patterns, as well as provide baseline data for developing benchmarks This slide shows an example of setting the application log format using the asadmin command in glassfish. Note that the trace attribute is useful in tracing a single request through multiple distributed systems to identify performance problems