Runpod•3mo ago

Workers and rate increasing

Hello everyone, can someone explain to me how the number of workers affects the increased consumption? Because, as I understood, even if there are 100 workers, it will not affect the cost of money, because the same capacities will be used. But it seems to me that I'm wrong, because it's strange?..

Dj•10/10/25, 8:57 PM

Lets say you have 5 workers running for a day straight. You can calculate your cost will be the hourly of the selected GPU Type * 24 (for 1 day) * 5 workers. A higher number of workers changes how much you're prepared to spend if we need to automatically scale you up times 5.

Jason•10/11/25, 2:18 AM

1 worker second = your gpu type price / seconds, excluding network storage too btw

DDj Lets say you have 5 workers running for a day straight. You can calculate your c...

Evgeniy_WisOP•10/11/25, 11:27 AM

This is understandable, but if I have a situation where workers work several times a day, "rarely but effectively." I need them to generate images using Fooocus. I always have, for example, 100 images to generate. 5 workers can do it in an hour. 10 workers can do it in half an hour. But it will cost the same amount of money, right?

Jason•10/11/25, 11:50 AM

Oh yess... Aslong total running time is the same

Jason•10/11/25, 11:50 AM

It's charged per second worker running

JJason Oh yess... Aslong total running time is the same

Evgeniy_WisOP•10/11/25, 12:11 PM

Well, thanks! I wonder why everyone doesn't take as many workers as possible if it's literally a free boost of speed

EEvgeniy_Wis Well, thanks! I wonder why everyone doesn't take as many workers as possible if ...

Jason•10/11/25, 12:15 PM

i think most of them do especially for production :)

JJason i think most of them do especially for production :)

Evgeniy_WisOP•10/11/25, 12:16 PM

Sorry, I didnt understand?..

Jason•10/11/25, 12:33 PM

I think most of people do take as many workers as they need to scale and respond fast to their app

EEvgeniy_Wis Well, thanks! I wonder why everyone doesn't take as many workers as possible if ...

Darki•10/11/25, 6:23 PM

because if you get flooded with 1000 requests then you get Huge amount of workers and begin paying some ridiculous amount of money per second when ur users can just wait in a 20s queue and you'll pay a fraction of the price

Darki•10/11/25, 6:24 PM

So unless ur running some overcharged ridiculous specialized serivce then it really doesn't make sense to have as many workers as possible

DDarki because if you get flooded with 1000 requests then you get Huge amount of worker...

Evgeniy_WisOP•10/11/25, 7:46 PM

Why? For example, we have 1000 requests and 1000 workers, and we have, for example, 1000$/sec. But if we have 500 workers, we will have 500$/sec, but we will have 2 sec, so you will pay the same 1000$. Am I missing something?

EEvgeniy_Wis Why? For example, we have 1000 requests and 1000 workers, and we have, for examp...

Darki•10/11/25, 7:55 PM

Cold starts

Darki•10/11/25, 7:55 PM

Depending on what ur running can take up a LOT of time

DDarki Depending on what ur running can take up a LOT of time

Evgeniy_WisOP•10/11/25, 8:50 PM

Hm, i understand. Well, it will be harder to count than i think...

DDarki Cold starts

Jason•10/11/25, 11:59 PM

Ah and this too, makes sense because runpod also saves you startup time if you have constant requests

(Flashboot)

Workers and rate increasing

Similar Threads

Similar Threads

Similar Threads