How to Reduce Costs from Idle Amazon Redshift Clusters
By
Nabarun Bandyopadhyay
Summary
This article discusses how Amazon Redshift clusters are often over-provisioned and idle for the majority of the day (up to 85% of the time), leading to unnecessary cloud costs. It highlights the gap between peak and average usage, explains how Redshift's always-on billing model charges for idle compute resources, and suggests strategies like auto-scaling, concurrency scaling, and serverless options to optimize costs and improve efficiency.
Source
Key quotes
· 3 pulledYour Redshift cluster is probably idle most of the day and billing you for all of it.
Most Redshift clusters are provisioned for peak load, but average utilization is far lower.
You're paying for compute capacity that's doing nothing useful for the majority of the time.
You might also wanna read
How Digital Society Reduced Cloud Costs by 76% While Tripling Capacity with Hetzner Migration
Digital Society, a not-for-profit cooperative, successfully migrated their cloud infrastructure from AWS and DigitalOcean to Hetzner, achiev
digitalsociety.coop·8mo agoRunning a Lucene Search Engine in AWS Lambda: Technical Challenges and Performance Results
The article describes an experimental approach to running a real search engine in AWS Lambda functions, challenging the conventional wisdom
Developer Saves 10x Costs by Moving Projects from AWS to Self-Hosted Servers
The article details a developer's experience moving all their projects off cloud services (specifically AWS) to self-hosted servers, resulti
Wozz: Kubernetes Cost Optimization Tool for Preventing Resource Waste
Wozz is a Kubernetes cost optimization tool that helps engineering teams reduce cloud spending through two main approaches: a PR Cost Linter
AWS Increases GPU Instance Prices by 15% Over Weekend
AWS has quietly raised prices on its EC2 Capacity Blocks for ML instances by approximately 15% over a weekend, specifically on a Saturday. T
AWS Budgets' Multi-Hour Delay Fails to Catch Rapid Bedrock Cost Spikes
This article exposes a critical flaw in AWS Budgets: it can have up to an 8-hour (or more) delay in alerting users about AWS Bedrock spendin
