Performance Hits for Caching Data in Memory

Question

Using the runtime in-memory cache in ASP.NET, what are the potential pitfalls of storing data? How much data is "too much" generally, and on what scale?

Answer 1

After getting around to testing some code which intensely uses the cache, there is no appreciable impact on performance that I can measure. It seems that when the cache approached memory limits, it simply kicks the oldest content off early, and so the performance impact is negligible.