All Things WebSphere
Concerns and issues relating to all versions of WebSphere Application ServerSaturday, September 20, 2008
Improving performance of your web application by 2x - 5x
Caching is a very common design pattern to improve the performance of a web application. Caching can be done at multiple tiers, application, database, edge of the network.... Caching done right can improve the performance of your web application by 2x-5x. Yes sir that is correct!!! Let me lead you to the road of redemption.
Say your application is an old school J2EE style application composed of with JSP, Servlets, JSF et al. Most of the time your app. is housed in an application server. All application servers have caching frameworks that you can leverage to cache web application JSP/JSTL/Servlet responses.
One hint of caution about adding more caching....Please look at JVM heap usage before you start caching the whole world. Please also put in place a cache invalidation strategy. You dont want users to buy an out-of-stock item.
More on these pesky cache issues later.....
Say your application is an old school J2EE style application composed of with JSP, Servlets, JSF et al. Most of the time your app. is housed in an application server. All application servers have caching frameworks that you can leverage to cache web application JSP/JSTL/Servlet responses.
- Look at your web application and determine what is cacheable and what is not. This is not an enjoyable activity. Its like asking someone what they want to become after growing up. At least try to determine all the obvious fragments of your site like headers, footers or relatively unchanging JSPs etc.. that can be cacheable.
- Employ tag libraries or configure servlet caching to start caching the web responses from these cacheable artifacts.
- Plugin a filter/handler/interceptor/thingamajig/custom code that interacts with caching framework that determines for every URI/request coming into the webcontainer, whether the request was a CACHE MISS, CACHE HIT or was UNELIGIBLE for caching.
- Log this information in some file and gather these statistics over a suitable period of time like a week.
- WTF do I do with this data ? 1. Determine the cacheability of your website. cacheability= no. of cache miss/no. of cache hits. The smaller this no. the better your website will be able to handle user load. 2. Most importantly look at all the URIs or requests that were demmed to be uncacheable and consider adding caching for those web fragment responses.
- Scrub and Repeat
One hint of caution about adding more caching....Please look at JVM heap usage before you start caching the whole world. Please also put in place a cache invalidation strategy. You dont want users to buy an out-of-stock item.
More on these pesky cache issues later.....
Archives
December 2006 September 2008 January 2009 February 2009 March 2009 September 2009 October 2009 November 2009 December 2009 January 2010 February 2010 March 2010 April 2010 October 2010 January 2011 February 2011 April 2011 May 2011 June 2011 July 2011 August 2011 September 2011 October 2011 November 2011 December 2011 January 2012 February 2012 March 2012 April 2012 May 2012 June 2012 July 2012 August 2012 September 2012 October 2012 November 2012 January 2013 May 2013 June 2013 July 2013 September 2013 October 2013 June 2014 August 2014
Subscribe to Posts [Atom]
Post a Comment
Note: Only a member of this blog may post a comment.