Amazon Redshift Concurrency Scaling

Get consistent, fast query performance for highly concurrent workloads

Why Amazon Redshift Concurrency Scaling?

Analytics workloads can be highly unpredictable resulting in slower query performance and users competing for resources. Customers need an automated, cost-effective solution that handles ever-changing query volumes without comprising performance.

With the Concurrency Scaling feature, you can easily support thousands of concurrent users and concurrent queries, with consistently fast query performance. As concurrency increases, Amazon Redshift automatically adds query processing power in seconds to process queries without any delays. Once the workload demand subsides, this extra processing power is automatically removed, so you pay only for the time when Concurrency Scaling clusters are in use. Amazon Redshift allows customers to scale with minimal cost-impact, as each cluster earns up to one hour of free Concurrency Scaling credits per day. These free credits are sufficient for the concurrency needs of 97% of Redshift customers. See the pricing page for more details.

With Concurrency Scaling you can:

  1. Get consistently fast performance for thousands of concurrent queries and users
  2. Allocate the clusters to specific user groups and workloads, and control the number of clusters that can be used
  3. Continue to use your existing applications and Business Intelligence tools.

To enable Concurrency Scaling, simply set the Concurrency Scaling Mode to Auto in the Redshift Console. Learn more


Customer Success

“We love how the Amazon Redshift team continuously adds features that make Redshift faster, more elastic, and easier to use. The latest new feature, Concurrency Scaling, instantly adds capacity to support additional users and removes it when the load subsides, with nothing to manage on our end. We’ve deployed this on all our Redshift clusters because it gives us the flexibility to handle the variance in our workloads over the course of a day without us having to intervene.”

Shahid Chohan, Software Engineer