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

Heroku does not support our current stop-line refresh process #191

Open
tkimia opened this issue Nov 13, 2019 · 0 comments
Open

Heroku does not support our current stop-line refresh process #191

tkimia opened this issue Nov 13, 2019 · 0 comments

Comments

@tkimia
Copy link
Collaborator

tkimia commented Nov 13, 2019

Right now, running a set-up-transitland through the heroku CLI results in a SQL error. This is because the SQL provider that we use caps us at 18,000 requests per hour. We need to re-do the rake task in a way that does not make so many SQL calls

Detailed Description

We use a lot of requests because we use the destroy_all function on stops, which has more than a 11 thousand stops.

Context

This change is not important in the short term, however, if we ever need to re-grab the data from transitland, our current process would bring the site down for multiple hours.

Possible Implementation

We might need to replace destory_all with delete_all. This only uses 1 query.

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

No branches or pull requests

1 participant