ASP.NET Micro Caching: Benefits of a One-Second Cache: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
ASP.NET Micro Caching: Benefits of a One-Second Cache

page 2 of 7

by Steven Smith
Feedback

Average Rating:

Views (Total / Last 10 Days): 50905/ 66

Article Contents:

Server and Test Setup

The test server had following specifications:

1GHz P3 Processor
512MB RAM
Windows Server 2003
SQL Server 2000

To test the page, I used Application Center Test (ACT), running locally. Everything in this test is running on one box, which I realize has some implications as far as where the bottlenecks in performance will occur. During all tests the CPU was maxed out, indicating that increased performance could have been achieved with a more powerful box and/or by splitting the work between several servers. However, the point of this test was not to achieve the maximum performance possible for this trivial example--it was to measure the effects of a small amount of caching on a simple but high-volume application.

The test script consisted of a single request to my default.aspx page. The script was constructed to use three simultaneous users for five minutes with thirty seconds of "ramp-up" time (to ensure the app had compiled and the sql server was awake and running full speed). ACT, unlike other tools such as LoadRunner, does not let you add "think time" between users' requests without editing the vbscript by hand, so although there are only three users, they are hammering the server because there is no delay between the completion of one of their requests and the initiation of their next request.

« (Page 1)

View Entire Article

(Page 3) »

User Comments

Title: Effective
Name: Sangam Uprety
Date: 2009-08-20 7:36:29 AM
Comment:
I tested the same using badboy and saw the differences myself. Page level output cache improves performance, like the caching of data in BLL. I just wonder why there is so few discussions on this technique. And is 1 second the minimum possible page output cache duration? Further, what about pushing it upto 10 seconds?

Title: good
Name: mcgyver
Date: 2009-07-08 1:14:06 PM
Comment:
my company is an equities broker and we have an ajax webbroker. There are about 100 more liquid assets, but 1000s of clients. Probably this aproach will diminish our hardware uses

Title: Simultaneous requests
Name: The Chief
Date: 2006-05-18 8:10:20 AM
Comment:
Hi

If it takes 0.5 seconds to load data and render the page and the server receives 20 requests within this time, does asp.net hold off processing the other 19 requests for the same page until it has finished rendering and caching the output from the first of these 20 page requests?

Your results would suggest that this is indeed what is happening but would appreciate confirmation of this.

We use caching on a busy e-commerce site, but there is still a bit of a hit on the server when the site restarts as all the output on each different category page is loaded and cached at the same time. I'm wondering whether the same data is being loaded twice via multiple requests.

Thanks

Title: Caching
Name: Arpi
Date: 2006-02-09 6:57:03 AM
Comment:
This article explain right.Hence I want to know how can we stop caching of the system

Title: Not So Silly
Name: Steven Smith
Date: 2005-07-28 8:32:35 AM
Comment:
Not so - consider a news site like CNN.com. With their traffic I'm sure certain articles are read more than 1/second, and I'm willing to bet their articles are stored in a database. The same is true for an eBay auction nearing its end, or a popular Amazon.com book. There are plenty of large scale applications that could theoretically benefit from this technique. That said, you have to test your own application using realistic usage data for your app, then set the cache duration to something that makes sense for you.

Title: Silly
Name: Cookie Monster
Date: 2005-07-28 3:05:54 AM
Comment:
This is silly. Only in this test would a 1 second cache make this large of a difference. In the real world, users wouldn't be accessing the exact same piece of data so often, so basically every request would end up a cache miss.

Product Spotlight