All,

We have a lot of custom content for a lot of clients all using the same web application. Right now we have about 3,000 API cache items and it's only using about 270 meg of ram (We have /3GB).

Instead of calling the DB many times per page, we are wanting to take a lot more of our business objects and store them in cache (All strongly typed smaller objects). I figure it can't hurt to utilize the RAM we have and lessen the load on the CPU.

Questions:
1) Is there a practical limit to the # of cached objects as long as there is RAM?
2) When an item is rolled out of cache (by the sliding values expiring, etc.), what kind of impact is there? Do those old cached objects get thrown into the GC heaps? And are they Gen 2 Collections?

Thanks,

[quoted text, click to view]
You mean database right? and not cpu?

[quoted text, click to view]
is RAM?
right
[quoted text, click to view]
etc.), what kind of impact is there? Do those old cached objects get thrown
into the GC heaps?
right

[quoted text, click to view]
Sliding experiation isn't related to a particular generation. Generations
are created strictly on the basis of the number of times the garbage
collector runs and whether or not the garbage is collectable or not. This
means necessarily that an expired cache object can, in theory, belong to any
generation.

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
[quoted text, click to view]
web application. Right now we have about 3,000 API cache items and it's
only using about 270 meg of ram (We have /3GB).
[quoted text, click to view]
lot more of our business objects and store them in cache (All strongly typed
smaller objects). I figure it can't hurt to utilize the RAM we have and
lessen the load on the CPU.
[quoted text, click to view]
etc.), what kind of impact is there? Do those old cached objects get thrown
into the GC heaps? And are they Gen 2 Collections?
[quoted text, click to view]