Co-Loc versus Dedicated In-Role Cache - both available to all instances?

Category: azure management


DigitalMan2112 on Thu, 13 Mar 2014 12:49:11

Trying to confirm that this is true. The only real difference between the co-located and dedicated in-role cache is that the co-located shares the memory with the role whereas the dedicated uses all the memory of the role. I'm assuming that even in a co-located cache the cache is synced and not per instance? Meaning if I set up a co-located cache on my web role and that role has multiple instances, the cache will be the same for all instances (objects added to cache from one instance would be available in all instances). 



Yuan2013 on Fri, 14 Mar 2014 02:27:04


Yes you are right.

Jambor yao on Fri, 14 Mar 2014 03:22:25


We can see this from Role Cache FAQ (Windows Azure Cache).

Here is a snippet.

What is the difference between co-located and dedicated Caching topologies?

There are two main ways a role can host In-Role Cache: co-located and dedicated. In the co-located topology, the role that hosts In-Role Cache also hosts other web role or worker role functionality. The memory and resources of the role are shared between caching and non-caching application code and services. In the dedicated topology, which is supported for worker roles, the worker role only hosts caching. These Cache topologies differ primarily in the percentage of memory that is dedicated to Cache. For more information, see the topics on co-located Caching roles and dedicated Caching roles.

Best Regards