Dear All,

not being able to find a appropriate "point of touch" with ms I try this forum.

We encounteder a problem regarding Azure Caching Services in our pilotphase-before-prod-(hint: big prospect... ;) )system:

Pre:

We use co-located caching in our project -cachesize: 30% (default) -Eviction: LRU -Expiration Type: Sliding Window

-Time To Live: 30

Our problem is that regardless we touch the caching service or not, the service memory consumption grows, and oversteps the 30% limit (grows over 2 Gb), resulting that the medium instance (with memory of 3.5 Gb) is unable to activate any service, because the available memory is under 5%.

Our question is: are we missing a point, why the caching service grows out of it's bounds, or is there a memory leak somewhere in the service?

We also found an unanswered article on stackoverflow with the same issue.

(http://stackoverflow.com/questions/16776823/why-does-azure-cahce-use-more-that-30-memory) Thank you in advance

Hi,
 
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
 
Thanks,