No available workers
All of my workers have been throttled. Is this expected?
That only 1 left sometimes back to throttled and then back to initialization stage and downloading the image, back and force.
6 Replies
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
I think it's the algorithm has changed, to more aggressively make the worker throttled. I already changed the region to be almost all, and I see it's high supply for my machine
And I am not sure if machines switch the state between idle and initializing is an efficient way of doing the scheduling, isn't downloading and remove the image a resource consuming thing to do?
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
At first, since I was only using 6 machines, there was only 1 idle/available machine, which made me nervous.
I also noticed that the request delay increased when I sent more requests at the same time, since the machine comes from throttled to idle and can be used.
But now, I see that 9 out of my 10 machines are idle. Not sure if runpod adjusts the algo during the time, but this does look much better.
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View