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

"OPTIMIZE TABLE" run on schedule can cause too much load on DB server #1192

Open
justingit opened this issue Dec 16, 2024 · 0 comments
Open

Comments

@justingit
Copy link
Owner

This is mostly because it's run every "x"minutes, rather than every week or few weeks.

It would be better to only optimize the table when there has been a very large amount of table rows that have been deleted since the last optimization. (we optimize mostly to save disk space)

We could keep track of rows deleted in the settings db under a new setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant