We know that designing a web application that is both scaleable and high
performance is difficult.
Scalability implies lots of web servers all referring back to a central SQL
server, which in turn implies limited caching which in turn hurts

I set outputcache to 30 minutes for all .aspx pages on my asp.net 2.0
websites. If a search engine (such as Google) crawl my site, it can hit
thousands of pages within a few minutes and thus produce a large amount
of page caches. This could use a lot of memory and impact other

Cache doesn't not work on my web application :(
I have 1 giga memory on server. 80% of memory is free.
But each time i put an object in cache, 1 second after item is removed
with "Underused" reason.

Is there any reason to cache an aspx page that only has static text on it?  
It doesn't make a db connection, but is accessed frequently.  I use an aspx
page instead of an html page to inherit the theme and master page for the
website.

The Docs for Cache say that member functions aren't necessarily thread-safe.
Does HtppRuntime.Cache return the same Cache object for any thread? If so,
then wouldn't this be a dangerous threading issue?
How is Caching implemented? Are Cache.Get and Cache.Insert thread-safe

I am using the command notification in my ASP.NET 2.0 web app.  I am
connecting to a Sql 2005 server.  I was able to get my Cache object to
invalidate based on the SqlCacheDependency object associated with it.  The
problem is I had to give the database use sysadmin rights in ...