Question

A retail analytics team runs an Amazon Redshift cluster that performs well most of the day. However, every morning between 8 AM and 10 AM, hundreds of business users run dashboard queries simultaneously, causing queries to queue and dashboards to load slowly. The rest of the day the cluster is lightly used, and the team does not want to permanently resize the cluster or pay for extra capacity outside the peak window. Which approach best resolves the morning slowdown while minimizing cost?

Accepted Answer

Enable Concurrency Scaling on the WLM queue used by the dashboard queries so Redshift automatically adds transient capacity during query spikes.

Answer

Resize the cluster to add more nodes permanently to handle the peak concurrency each morning.

Answer

Increase the number of query slots in the WLM queue so more queries can run at once on the existing nodes.

Answer

Enable short query acceleration (SQA) to prioritize the dashboard queries ahead of longer-running jobs.