You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.
Number 7 from that list, queries that are disk-based, appears to be something we're suffering from. I ran the diagnosis query and there was a heap of results. It can be fixed by increasing the amount of memory available to each queue, but that involves some level of poking about in the AWS console that I'm not entirely comfortable with.
Raising it here so we can discuss whether to address it.
The text was updated successfully, but these errors were encountered:
In light of #72, I've been going through the common performance problems listed here:
https://aws.amazon.com/blogs/big-data/top-10-performance-tuning-techniques-for-amazon-redshift/
Number 7 from that list, queries that are disk-based, appears to be something we're suffering from. I ran the diagnosis query and there was a heap of results. It can be fixed by increasing the amount of memory available to each queue, but that involves some level of poking about in the AWS console that I'm not entirely comfortable with.
Raising it here so we can discuss whether to address it.
The text was updated successfully, but these errors were encountered: