Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VACUUM tables #225

Open
alok87 opened this issue May 15, 2021 · 1 comment
Open

VACUUM tables #225

alok87 opened this issue May 15, 2021 · 1 comment
Labels
p3 not urgent, intermittent issue performance Monitoring, Metrics, Logs, Benchmarks

Comments

@alok87
Copy link
Contributor

alok87 commented May 15, 2021

Tables in Redshift needs to be vacuumed for peak performance. Auto VACUUM might not be helpful always.
https://docs.aws.amazon.com/redshift/latest/dg/r_VACUUM_command.html
https://docs.aws.amazon.com/redshift/latest/dg/t_Reclaiming_storage_space202.html
https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_TABLE_INFO.html

select "table", unsorted,vacuum_sort_benefit from svv_table_info order by 2 desc;

Can operator perform nightly vacuums on tables which have many unsorted and uncleaned data?

AWS does provide auto vacuuming, but we knowing the time of load and time when we want peak performance we can enable vacuuming from the operator.

@alok87 alok87 added the performance Monitoring, Metrics, Logs, Benchmarks label May 15, 2021
@alok87 alok87 added the p3 not urgent, intermittent issue label Jun 17, 2021
@alok87
Copy link
Contributor Author

alok87 commented Jun 17, 2021

p3 since aws already does it well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3 not urgent, intermittent issue performance Monitoring, Metrics, Logs, Benchmarks
Projects
None yet
Development

No branches or pull requests

1 participant