Not using cached worker
I've been running into this problem for several days now. I have a endpoint that runs a forge webui worker with a network volume attached. And as you know forge takes some time to start and only then generates the image. So generally when I send a request to a worker it takes some delay for the start process then generates images.
But recently I've run into an issue where there is already a worker running with webui forge started and ready to accept requests but when I submit a new request it completely starts a new worker, which results in huge delay times. My question is, why isn't it using the already available worker which has forge loaded?
And no, the requests weren't submitted one after the other so there is no reason to start a new worker
13 Replies
for anyone who needs some clarification of the image the logs are from the worker highlighted in grey color. It already has forge loaded. But as you can see there is a completely new worker running, ignoring the worker that has forge loaded
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
This is my endpoint scaling type, should I change anything?
a long time. For example if I submit a request at 5:00PM it loads forge and run it, and then if I submit again at about 5:03PM instead of running the request in the worker that has loaded forge it runs it on a new worker
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
yes the worker that has forge loaded is still available, has no requests running. I can check it from the logs and the logs say it has forge loaded
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
I'll try that I wanted to keep costs reduced but I don't want unavailable workers and long startup times either
also is there a way to cancel a job if delay is too high?
currently I manually cancelled these but it would be nice if there is an automated way to do it
unfortunately Enable Execution Timeout doesnt work for delay times only execution times
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
thanks I just looked at the documentation I think I'll be able to do that
btw for image generation tasks what is best - run or run_sync?
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View