-
Notifications
You must be signed in to change notification settings - Fork 5
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
Move Off Heroku? #9
Comments
or you could just start paying the $7 a month to Heroku so it is always on... I suspect you could get this for free for a UG if you happened to know of somebody that worked at Heroku you could ask ;) |
Ha ha, nice! I'll see if I can think of someone ;-) |
When you say "slow", how long? shouldn't be any more than a few seconds...depends on how long your app takes to come up... |
It is just a few seconds - nothing dramatic, just noticeably slow. This wasn't something I was desperate to do - just something I was considering in the long-term. |
Is it the container, or the app that's taking a while? :-) |
It's the container - the first load is very slow before anything is returned, then everything is sent at once. The second load (not using the cache) is much faster. I'm not saying the app couldn't be faster - but that isn't what this is. |
but the app startup will be a bit part of that first load, I think that is what @bigkevmcd is getting at. |
I see what you mean. It's pretty much a moot point, isn't it? The app gets spun down when not in use, so when someone accesses the site after it's been dormant for a while it takes a while to respond. |
The container startup time on Heroku is pretty slow. Maybe the site should be moved onto an EC2 instance.
The text was updated successfully, but these errors were encountered: