Closed ecnmst closed 10 years ago
Yes, this is a problem with the way we are using heroku. The instance (our server) is being shut down if no one is using the website. When someone accesses the link, the instance is being rebooted. That's why its taking a lot of time to boot the first time.
We can fix this by asking for 2 instances that are always up. That would cost 35 $/month
In that case it's fine. Coz it means it won't be a problem if there are users around, so it's good practice to save resources.
On Wed, Sep 3, 2014 at 12:43 PM, Daniel Hasegan notifications@github.com wrote:
Yes, this is a problem with the way we are using heroku. The instance (our server) is being shut down if no one is using the website. When someone accesses the link, the instance is being rebooted. That's why its taking a lot of time to boot the first time.
— Reply to this email directly or view it on GitHub https://github.com/dhasegan/connect.academy/issues/123#issuecomment-54279313 .
I will close this since it is not something we will work around
This delay happens when you were logged in and it resumes with you logged in. When you do it as signed out users, it is quicker. Then if you go to the site a second, third time etc, there is are NO delay issues.