Node Size

Compute Resources

You can choose a node size that matches your caching workload and performance requirements. For Redis, memory capacity is especially important, as all cached data is stored in memory.

If you expect to handle large datasets, high request rates, or complex data structures, consider selecting a node size with higher RAM (such as the “r” series). For lighter workloads or cost-efficient setups, a smaller configuration (such as the “b” series) may be sufficient.

Basic (b)

Provides a balanced configuration suitable for general-purpose caching workloads.

All-purpose (a)

Offers a versatile configuration with increased memory, suitable for moderate caching workloads and mixed access patterns.

RAM-optimized (r)

Designed for memory-intensive caching scenarios, such as large keyspaces, high cache hit rates, or complex in-memory data structures.

vCPU: The number of virtual CPUs allocated to the Redis instance. More vCPUs can improve performance for concurrent connections, background tasks, and network throughput.

vRAM: The amount of memory available for storing cached data. Since Redis operates primarily in memory, sufficient RAM is critical for achieving high performance and avoiding evictions.

Changing the node size will briefly interrupt the service, as the instance is restarted with the new resource allocation.

Storage Size

The disk size can only be increased. To reduce it, you must create a new CaaS instance and migrate your data.

Each Caching-as-a-Service (CaaS) instance requires a minimum disk size of 50 GB. You can increase the disk size in increments of 50 GB up to a maximum of 500 GB.

Increasing the disk size does not interrupt the service.