This article provides answers to common questions about how to plan for Azure Cache for Redis.
For guidance on how to benchmark Azure Redis cache performance and for sample benchmarking numbers, see Performance testing.
For details about Azure Redis billing, see Azure Cache for Redis pricing. The pricing page lists pricing as an hourly and monthly rate. Caches are billed on a per-minute basis. The billing period is measured from time a cache is created until the time that the cache is deleted. There's no option for stopping or pausing cache billing.
The Basic, Standard, and Premium tiers of Azure Redis are available in Microsoft Azure operated by 21Vianet Cloud.
| Cloud | Domain Name System (DNS) suffix for Redis |
|---|---|
| 21Vianet Cloud (China) | *.redis.cache.chinacloudapi.cn |
The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
For more considerations about using Azure Redis with other clouds, see the following links:
For information about using Azure Redis with PowerShell in Microsoft Azure operated by 21Vianet Cloud, see How to connect to other clouds - PowerShell.
In Azure Cache for Redis, your application data is stored in the RAM of the virtual machine (VM) or VMs, depending on the tier, that host your cache. By default, your data resides in the Azure region you selected. There are two cases where your data might leave a region:
When you enable data persistence on a Premium-tier cache, Azure Cache for Redis backs up your data to an Azure Storage account. If your storage account is in another region, or replicates data through geo-redundant storage (GRS) to a different region, a copy of your data ends up there.
If you set up passive geo-replication on a Premium-tier cache and your secondary cache is in a different region, as is typical, your data is replicated to that region.
You need to explicitly configure Azure Redis to use the preceding features. You also have complete control over the region where the storage account or secondary cache is located.
For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
See other Azure Redis FAQs.