Redis Cloud Throughput Sizing Decision Guide: Optimize, Increase, or Upgrade

In Redis Cloud, database throughput defines how many operations per second (ops/sec) can be processed within your latency targets. Throughput limits vary by plan, and Free Redis Cloud Essentials is capped at 100 ops/sec. When performance doesn’t meet workload demand, it’s critical to determine whether to optimize the workload, increase throughput, or upgrade your plan. This guide provides a clear decision framework to help Redis Cloud users identify performance bottlenecks, choose the right scaling path, and validate results across Free Redis Cloud Essentials, Essentials, and Pro subscriptions.

Covered: Identify the Bottleneck, Choose the Path, Validate and Monitor, and Plan Differences.

Prerequisites

• Active Free Redis Cloud Essentials, Redis Cloud Essentials, or Pro subscription

• Access to Redis Cloud Console metrics

• Familiarity with throughput targets, request size, and latency goals

Step 1: Identify the bottleneck

The first step is to determine what limits throughput or increases latency within the current workload.

• Benchmark latency and throughput to set realistic ops/sec targets.

• Check request size, command complexity, replication/TLS, and client connection count — all affect throughput.

• Use SLOWLOG or Redis Insight to surface heavy commands.

redis-cli SLOWLOG GET [count]

Step 2: Choose the Path

Once bottlenecks are identified, choose the best corrective action. Always start by optimizing the workload before modifying throughput or plan settings.

If you're using Free Redis Cloud Essentials and consistently reach 100% throughput utilization (100 ops/sec), optimization options are limited. Sustained throughput above this limit requires upgrading to a paid plan.

Path A: Optimize First

• Simplify commands and reduce payload size (especially if average request size >3 KB).
• Enable pipelining to minimize round-trip latency.
• Identify and reduce heavy operations using SLOWLOG or Redis Insight.
• See Redis Performance Tuning Best Practices.

Path B: Increase Throughput

• Increase the configured ops/sec value in the Redis Cloud Console (Database → Performance → Throughput).

  • This option is available only on paid plans. Free Redis Cloud Essentials has a fixed throughput limit of 100 ops/sec and does not support throughput configuration changes.

• Benchmark under realistic load and monitor latency improvements.

• Essentials plans are capped by tier. To raise throughput, upgrade to a higher tier. See Essentials Plan Details.

• Pro plans allow configurable throughput. Throughput and memory settings determine your Redis Billing Units (RBUs), which directly affect cost. For plan details, see Pro Subscription.

• Continue monitoring ops/sec, latency, and CPU usage after changes, and set alerts for any regressions.

Path C: Change Subscription Type

• If your workload exceeds Essentials limits, upgrade to Pro for configurable throughput and advanced performance tuning.
• Follow Upgrade from Essentials to Pro.

For deeper sizing and capacity guidance, see Undersized Redis Cloud Databases: How to Diagnose and Fix, Oversized Redis Cloud Databases: How to Right-Size Safely, and Redis Cloud Database Sizing.

Plan Differences

Reaching 100% throughput utilization on Free Redis Cloud Essentials indicates the hard plan limit has been reached and may result in throttling or increased latency until usage drops or the plan is upgraded.