I'm currently using a PostgreSQL 16 database on an RDS instance that has 16 vCPUs and 64 GB of RAM. I've recently received a medium severity warning from AWS, indicating that my instance is generating too many temporary objects. They suggested considering workload tuning or switching to an RDS instance class that supports Optimized Reads. I'm looking for advice on where to start troubleshooting the excessive temp objects. What specific settings should I investigate or adjust? Also, keep in mind that my main table is quite large and involves heavy joins and annotations.
3 Answers
It looks like your queries might be demanding a lot of temporary working memory. I recommend using Postgres Analyze to check out the joins with table scans that don't have filters applied. Filtering your data before performing joins can really help minimize the amount of data pulled into memory. If tuning your workload doesn't seem feasible, consider increasing the `work_mem` setting to allow more temporary memory per query.
I don't have a direct solution, but I'm curious about the size of your database and how many queries you're running that require such a hefty RDS setup with 16 vCPUs and 64 GB of RAM. That seems like quite the workload!
Here are some useful links that might help you out:
- https://aws.amazon.com/products/databases/
- https://aws.amazon.com/rds/
- https://aws.amazon.com/dynamodb/
- https://aws.amazon.com/aurora/
- https://aws.amazon.com/redshift/
- https://aws.amazon.com/documentdb/
- https://aws.amazon.com/neptune/
Also, check out this [search](https://www.reddit.com/r/aws/search?q=flair%3A'database'&sort=new&restrict_sr=on) for more discussions on similar topics.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically