-
Notifications
You must be signed in to change notification settings - Fork 71
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
Decrease size of HistoricalLink table #3008
Labels
Comments
We're trying a customized version of the duplicate cleanup command on a clone of the prod db, to see how much it reduces the final size and how long it takes, on a db where nothing else is happening. For this experiment, we're running it as a fab task in 4 tmux sessions on one minion; in real life we probably would run on the IA minions, maybe mediated by celery, maybe not? TBD.
|
matteocargnelutti
added
housekeeping
Issue type
database
Subcategory
priority-low
Priority hint
labels
Aug 9, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use Django Simple History to track changes on a number of our models. The historical link table is huge:
The routine creation of a link makes 3 rows, one of which is a duplicate which I think
clean_duplicate_history
will remove.Maybe let's try running that, and see how it goes? The table is so big, I'm not sure it will run painlessly, but we can hope. We probably want to run it regularly, maybe as an hourly/daily celerybeat task.
Also, Jack says, "seems totally viable to
clean_old_history
with some long time window, too."The text was updated successfully, but these errors were encountered: