Home arrow Zend arrow Page 5 - Improving Performance

Client-side caching - Zend

Your web presence is growing! Traffic and usage are escalating and you have to maintain a superior level of performance. The state of growth unfolds many opportunities but it also holds challenges as a result of change. Not only does performance affect your operating costs, it also reflects directly on the end-user experience. The marketing and sales departments are probably saying that happier users directly increase sales.

TABLE OF CONTENTS:
  1. Improving Performance
  2. Static and Dynamic Web content
  3. Reverse Proxy cache
  4. Code caching (Acceleration)
  5. Client-side caching
  6. Caching conditions
By: Zend
Rating: starstarstarstarstar / 8
January 08, 2004

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

Client-side caching is a feature that stores frequently used information on the client's machine. It provides performance enhancements on the client side by allowing the client to quickly access a file that would have normally be accessed from a server.. Client caching is especially effective when the client disconnects from the server, in that case files can still be accessed from the local cache. Client-side caching is usually defined in the client's browser settings.

Dynamic content caching maximizes performance and scalability
Dynamic content caching solutions address the scaling and performance issues of Web servers directly. They work well for heavily visited sites containing many dynamic features that must be tuned to respond quickly and easily. For a growing company anticipating reaching the Web server's maximum processing power, dynamic content caching solutions will expand the Web serverís capacity more effectively than adding additional hardware to manage the load. In certain cases, server-side dynamic caching may be 20 to 100 times faster than processing the page normally.

Two factors to keep in mind when considering whether to cache dynamic pages include frequency of content changes and demand level for current content (hit count). Anticipated hit count determines the prioritization of pages to be cache. More popular pages take precedence over less frequently accessed pages. Some caching solutions provide analysis of script popularity on the site.

Full page caching
Full-page caching is the simplest and most straightforward dynamic caching mechanism. The user defines which page to cache and the server stores it in the cache disk space. In subsequent request for the page, instead of parsing the page, running the script and building the HTML page, the server will locate the existing cached page and send it to the client. The home page for a Web site is an excellent example of a popular page for full-page caching. Generally it is the first page that users see, the most frequently accessed and therefore has the greatest impact on the user experience. As mentioned, when using dynamic content caching the web server no longer creates pages for each request, but sends pre-built copies to the clients. Therefore, users do not see content changes once a page has been cached. Introducing the concept of 'lifetime' settings can solve this problem while still maintaining huge performance gains, even when set as low as two minutes. Lifetime settings permit the server to discard cached pages once their defined lifetime has expired, forcing the application server to reprocess the pages.



 
 
>>> More Zend Articles          >>> More By Zend
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

ZEND ARTICLES

- Taking the Zend Certified PHP Engineer Exam:...
- Quick Introduction to PHP 5
- PHP SOAP Extension
- Improving Performance
- PDFs with PHP part 2
- PDFs with PHP part 1
- PHP at Lycos
- Build Database Interfaces

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: