-
Notifications
You must be signed in to change notification settings - Fork 8
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
Investigate more efficient Friday-night scraping approach #38
Comments
On Friday, we run full event and bill scrapes at the top of every hour. That means most of the regular full scrape is redundant. I propose we nix the regular full scrape on Friday and run only a person scrape, instead. This should remove the blocker! |
The full bill scrape took almost seven hours last night!!!
|
In other words, the slow full scrape blocked other scrapes for almost the entire support window. 😓 Manually ran a full event scrape to post agendas this morning.
|
We addressed this. |
We run full and windowed scrapes on Friday, however we preclude multiple scrapes from running at once, so in theory, a full scrape could block a windowed scrape and prevent recent changes from appearing for quite a while. Let's look into a Friday-night approach that balances efficiency with completeness.
The text was updated successfully, but these errors were encountered: