Do you get charged whilst your request is waiting on throttled workers?
I did everything I can to reduce cold start times on my end. I managed to install everything onto a Docker container (and avoid using Network Volume), and I'm using the official runpod A11111 worker with minor modifications.
Unfortunately the cold start times are still random. I noticed that despite setting 3 Max workers to an endpoint, all 5 workers would get the "Throttled" status, which I'm guessing is the reason why the cold start times are so random.
If I'm getting a very high request time due to Throttled workers, in this case, one basic request took 170 seconds - am I getting charged for the entire 170 seconds?...
All of the workers throttled even if it shows medium availability?
When we created an endpoint in a serverless manner, we noticed that none of our queries were being processed. When we looked inside the endpoint, we saw that all the workers were throttled. However, these machines appear to be available in terms of their availability status, how can we solve this?
Unreasonably high start times on serverless workers
I'm trying to deploy a serverless endpoint for A1111 instances using a preconfigured network volume. I've followed the steps shown in this tutorial https://www.youtube.com/watch?v=gv6F9Vnd6io
But my workers seem to be running for multiple minutes with the container logs filled with the same message "Service not ready yet. Retrying..."
Am I missing something here?...
Issue with Worker Initiation Error Leading to Persistent "IN_PROGRESS" Job Status
Hi All,
While testing the endpoint, I observed that when initiating a job with an empty input in the request body (using {"input": {}} or an empty JSON {}), the worker fails to start successfully. Despite this, the job status continually displays as "IN_PROGRESS".
This problem persists without reaching a resolution or a timeout state, necessitating manual intervention to cancel the job. The log output indicates an error message: "Job has missing field(s): input." However, the job status doesn't reflect this error and remains indefinitely in progress....
