I've had this heroku account for almost two weeks, but in the billing section my free dyno hours used this month remains at 0%. This isn't possible because I've set an uptimerobot to hit my heroku API every 29 minutes (to prevent it from sleeping).
Contemplating upgrading to Hobby so accurate info is nice to have here.
Related
According to heroku
Starting today, Heroku accounts have an account-based pool of free dyno hours for use on free apps. This replaces the 18 hours a day limit on free apps, allowing a free app to run 24/7 if needed. New accounts receive 550 free dyno hours and you can verify your identity with a credit card for an additional 450 hours
→ How are dyno hours calculated
If my app is always up, how many days will it stay up for (If I have 550 dyno hours) or does it depend on traffic and usage?
An app consumes hours based on their uptime, no matter the usage or traffic your app receives.
If you do the math, 550 hours is equal to 22.92 days.
If you were to add your payment method, it would give you a thousand hours, enough for a single app to run 24/7.
I have a question about running my Twitter bot 24/7, and I already have it uploaded to Heroku. The code works great.
However, the dynos will fall asleep after 30 minutes of non-use. This is great, however, my code is programming to tweet the same thing once a day.
In order to keep the dynos alive, the code has to be run every 30 minutes. The tweet, however, is the same thing once a day.
Is there a way to keep the Twitter code running when receiving a duplicate?
It seems like you want to bypass the limit, but that is not possible. if you keep running that service all day your free hours will expire.
Verified accounts come with a monthly pool of 1000 Free dyno hours; unverified >accounts receive 550. When a Free dyno is active, it draws from the pool; your free >apps can run as long as there are dyno hours left in your monthly pool.
instead, better to upgrade the Heroku to the premium version.
I have a website hosted on heroku. Whenever I load it for the first time after awhile (I haven't figured out the exact interval yet, be it days or hours), it takes upwards of 15 seconds to load. Subsequent loads are <1second, even if I clear the cache completely and open it in an incognito tab.
Why might this be? It almost seems like some kind of DNS issue but I haven't really got a clue. I don't know how to troubleshoot something like this. The situation seems to be the same even on other computers at other locations.
Quoting the Heroku docs:
If an app has a free web dyno, and that dyno receives no web traffic in a 30-minute period, it will sleep.
When the dyno receives traffic again, it will take a few seconds to wake up, hence the delay you've experienced.
Note that the Heroku free tier also has a maximum number of dyno hours per month. A sleeping dyno doesn't use any hours, but it does when it's active. When the hours are used up, the dyno won't wake up to incoming traffic.
You can see your remaining quota of dyno hours with:
$ heroku ps -a <app name>
Heroku suggests upgrading to a hobby dyno if your app needs to be permanently accessible. More info on https://devcenter.heroku.com/articles/free-dyno-hours
On the free tier, Heroku dynos go to sleep if they aren't used after an hour or something like that. They take a few seconds to wake up. Pay for the service and it stops happening, or write a script to ping your site every couple minutes or something.
If I only have one active app is it possible that it could spend all free Dyno hours quota?
My app is a PHP process which is always active (while (true) { do_something}). I launch this process as a worker.
I thought the free Dyno hours quota were like real hours so you can spent 24h as max per day. But if I view my remaining free hours quota in two consecutive days using 'heroku ps -a app' command then I get that I am spending more than 24h per day.
Another question, how many hours do you have in a Hobby plan?
If you are running 2 dynos (for example, a web dyno and a worker dyno), they will each use 24 hours, for a total of 48 dyno hours used in a day. Of course in reality it would probably be less than 24 hours each, if the dynos slept for part of the day.
I solved my problem disabling the web Dyno.
I have an app on the free heroku version, and want to upgrade to hobby, to avoid the 6 hours of required dyno sleep per day.
But I'm confused about the discrepancy between Heroku pricing page, and the info I get from running heroku apps:info in my app.
My app:
Add-on: heroku-postgresql (postgresql-angular-8...)
Plan: hobby-dev
Price: free
as: DATABASE
The above implies the app is already on hobby... which is confusing because I'm not currently paying anything, and the dyno sleeps 6 hours a day.
Heroku ( https://www.heroku.com/pricing )
Per Heroku pricing page, hobby is not free ($7 / dyno / month). And does not need to sleep.
I'd like to upgrade to the cheapest paid version that doesn't require dyno sleep and am confused.
Has anyone dealt with this and can clarify?
Your database in on the hobby-dev plan which has a row limit of 10,000 rows but your web server (dyno) is probably on the free plan. See here for more details.