-
Notifications
You must be signed in to change notification settings - Fork 0
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
Further increase frequence of the fill pk task in H #349
Conversation
"schedule": crontab(hour="*,9-12", minute="*/15"), | ||
"kwargs": {"batch_size": 10000}, | ||
"schedule": crontab(hour="*,6-12", minute="*/10"), | ||
"kwargs": {"batch_size": 15000}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe more, 50k?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How long is this going to take to complete given the current DB size and growth rate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this rate over two months, new annotations are not that important, we can (and should) soon update the code so they don't need this, setting the pk and user_id in python when they are created.
Start earlier, do the task every 10 minutes and for a bigger batch size
a600b73
to
7f15cd9
Compare
"schedule": crontab(hour="9-12", minute="*/15"), | ||
"kwargs": {"batch_size": 10000}, | ||
"schedule": crontab(hour="5-12", minute="*/10"), | ||
"kwargs": {"batch_size": 15000}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tasks have already gone over the time limit:
I don't think we should increase, 4 min is plenty of time. Looking at NR looks like the first run of the day it usually slow? I guess after that postgres makes room on ram for the indices?
Closed in favor of #351 |
Start earlier, do the task every 10 minutes and for a bigger batch size
See performance on new relic:
https://one.newrelic.com/nr1-core/apm-features/transactions/MTM4NTI4M3xBUE18QVBQTElDQVRJT058MjI2ODg2MzE?account=1385283&duration=604800000&state=fe611650-259d-7fd0-114a-8a0f8f31d672