title: Is MemoryCache scope session or application wide?
body: <p>I'm using <code>MemoryCache</code> in ASP.NET and it is working well. I have an object that is cached for an hour to prevent fresh pulls of data from the repository.</p>
  
  <p>I can see the caching working in debug, but also once deployed to the server, after the 1st call is made and the object is cached subsequent calls are about 1/5 of the time. </p>
  
  <p>However I'm noticing that each <em>new</em> client call (still inside that 1 hour window - in fact just a minute or 2 later) seems to have the 1st call to my service (that is doing the caching)  taking almost as long as the original call before the data was cached.</p>
  
  <p>This made me start to wonder - is <code>MemoryCache</code> session specific, and each new client making the call is storing it's own cache, or is something else going on to cause the 1st call to take so long even <em>after</em> I know the data has been cached?</p>