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
2 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
Is it like 1 second difference or it loaded like fron a long time ago?
Maybe the flashboot doesn't work everytime and keep it "warm" for a long time if your request are sporadic, or it's your endpoint scaling type that starts a new worker