Managing Caches (Azure Shared Caching)
Updated: June 19, 2014
|Please note the Azure Shared Caching service will be retired on September 1, 2014 and with it the Azure Silverlight-based portal. Once the Shared Caching service is retired, all remaining Shared Cache deployments will be deleted. Microsoft strongly encourages you to migrate at the earliest opportunity all existing Shared caches to either the Managed Cache Service (currently in GA) or to the new Azure Redis Cache (currently in Preview). For migration guidance, including guidance for migrating without making code changes, see Migrate from Shared Caching. For more information about the current Azure Cache offerings, see Azure Cache.|
Use the Azure Management Portal to manage caches for Microsoft Azure Shared Caching. This topic describes common management tasks associated with Shared Caching.
|The latest does not support the cache creation or management for Shared Caching. You must switch back to the previous portal.|
Cache Management (Shared Caching)
To create and manage caches, you must go to the Cache section of the .
On the main page of the Management Portal, click Service Bus, Access Control, & Caching at the bottom of the left pane.
In the left pane, expand Services, and then click Cache.
In the main window, you can create and manage caches. If you select an existing cache, you can see the cache details appear in the Properties window on the right side. These properties contain information that can be used to connect to and use the cache from any .NET application.
In addition, the toolbar provides other ways to interact with your cache. The View Client Configuration button brings up XML that can be used to configure the cache in an application configuration file or a web.config file. The Change Cache Size button allows you to change the cache size. See the next section on cache size for more details.
|You can only change your cache size once per day.|
When you create a cache or change its size, you have the option of setting the cache size to one of the following values:
This is the maximum amount of memory that can be used for the cache. However, it is important to understand that objects are serialized before they are placed in the cache. Serialized objects are always larger than their raw data, because they also contain type information and other metadata. Currently the amount of memory used in a cache is calculated as the size of the serialized objects in the cache rounded to the nearest 1 KB.
Each cache size also has an associated expectation on the type of network resources required. Larger caches expect that more network bandwidth is necessary to handle more objects going in and out of the cache. For more information about memory and network quotas, see Understanding Quotas for Azure Shared Caching.
The has several cache properties for monitoring Shared Caching.
Peak Size (this month)
Peak Size (last year)
In This Section
ConceptsAbout Azure Shared Caching