Home
Analytics
Analyze Web server logs for existing Web sites to identify traffic patterns using tools such as Perl scripts. This helps to identify important servlets to cache. Count the number of hits for each unique servlet URL, ignoring any request parameters. Servlets with a large number of hits are good candidates for caching. Group the hits by hour to find out which servlets were accessed the most at what time. These servlets must be in the cache at the right time in order to reap the greatest performance benefit.
Web server logs also show the content length, or size of the servlet request. When a servlet is cached, knowledge of its size helps us to fine tune the cache by setting an appropriate cache size in terms of cache entries. JVM performance is improved by reducing the amount of time spent doing compaction.
Use third-party analytics tools to identify servlets that should be cached. For example, use such analytics reports to determine which pages are hit most frequently by visitors to the site. If those pages are also suitable for caching, then modify the cache policy to cache those pages and improve performance.