 | | | |
| ASPCACHE BENEFITSBenefits
Discussion 20+ times faster than the ASP Application object Though ASP applications can implement data caching using the
ASP ASPCache is also highly optimized for page fragment caching - ASPCache avoids overhead from BSTR allocation, Unicode conversion, COM object creation, file access, and script execution. Real-world ASP pages using ASPCache page fragment caching can run at 800 requests per second on Quad processor Web servers. 300+ times faster than the Commerce.Dictionary Compared to the Site Server Commerce.Dictionary, ASPCache offers superior performance and better features for caching. Improves Web site performance Web server caching improves Web site performance by skipping repetitive work and using cached results instead. ASPCache provides outstanding functionality for data caching and output caching. Web site designers can choose which type(s) of caching to use for a given page. Caching Web page output (also known as Page Fragment Caching) yields the best performance, but requires that the same page fragment can be displayed in multiple requests. Data caching is valuable when the data can be re-used in later requests. Caching trades storage to save processing cycles; by storing past results, the hope is that future processing can be skipped. The value of caching is compromised when items are out-of-date, when extra storage becomes scarce, and when cached results are rarely used. ASPCache solves these issues with item expiration, cache shrinking, and flushing underused items. Easy to add to existing ASP sites ASPCache is easily added to existing ASP sites by adding an <object> tag to the global.asa file:
REM *** global.asa *** Once the <object> tag is added, any ASP page can cache and retrieve data stored in the ASPCache object. If the ASP site previously used the
Application object
for data caching, all such usage can be converted to ASPCache by globally replacing " To add page fragment caching to an existing ASP page:
| ||
