Do two heroku apps running concurrently consume dyno hours faster? [duplicate] - heroku

This question already has answers here:
How is it possible to use 1000 Heroku Dyno hours in one month?
(1 answer)
What exactly is dyno hour on Heroku?
(1 answer)
Closed 9 months ago.
I have two apps front-end and back-end that run at the same time. Will it consume dyno hours faster? E.g. Running two apps at the same time for two hours consume four dyno hours? Thank you. I'm a beginner at Heroku.

Related

How can I calculate dyno hours?

I recently finished making a discord bot and am ready to push it to production. I need to use 2 dynos, one is a worker (node index.js) and the other is a web worker. Because I am using two dynos, are double my dyno hours used or are the dyno hours calculated across the whole app? I ask because I want to use the free 550-1000 hours per month.

Why is heroku dyno consuming a bunch of hours?

So I currently have a Java Spring Boot app deployed on Heroku and is the only dyno I have deployed on the account. I had made a call to it and it started up the server but then immediately logged ~1.2 hours off of my free dyno hours. I only had it open for ~10 minutes and then with the added 30 minutes to go to sleep it should only have logged 40 minutes. Is it possibly because it is making multiple calls to the same dyno that it is spinning up multiple thread and then charging double? What causes this?

Heroku Free Tier - Can a single app spend all Dyno quota?

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.

Issue with Heroku's production configuration: a set of two dynos takes 8 seconds to respond

I have an interrogation regarding Heroku's dynos.
As of now my app runs two 512MB dynos and I was pretty certain that this configuration, i.e. more than one dyno, ensured that the container's application was started and ready to serve clients.
However, I frequently notice that the dynos are not always started and it takes something like 8 seconds to load the app. See screen shot below. The host XXXX.herokuapp.com spends nearly 8 seconds in "waiting".
Has anyone else experienced such issues with Heroku? How can they be resolved?

Are the dyno restarts on Heroku simultaneous?

I read on Herokus website that dynos will be restarted about every 24 hours.
If you have for example two web-dynos is there a chance that they will be restarted simultaneously?
Thanks for your time!
According to heroku:
"The cycling happens once every 24 hours (plus up to 216 random
minutes, to prevent every dyno for an application from restarting at
the same time)."
Source: https://devcenter.heroku.com/articles/dynos
Heroku restarts dynos randomly -- sometimes multiple times per day. Don't count on it being simultaneous!

Resources