I am developing an application for windows azure using the latest SDK.
At the moment I am implementing the session provider using the cache, but the simulator is completely out of proportion:
The cache is implemented as a "very small" worker role (max. 768 MB RAM).
Does anyone know if this is normal or if I have some misconfiguration?
While I can't say if this is the "right" behavior but I am also seeing the same. In my case, cacheserviceemulator.exe starts at about 300KB memory and keeps on consuming more and more memory. What I have been told is that it is expected behavior. This service is expected to
consume up to 30% of your system's memory
over an extended period of time.One other note: I noticed that you're using
X-Small
Size instance for cache worker role. Please note that minimum size supported for caching isSmall
. Thought I should mention that as well.