vesper
RRunPod
•Created by vesper on 2/1/2025 in #⚡｜serverless
Job Never Picked Up by a Worker but Received Execution Timeout Error and Was Charged
I set the execution timeout to a maximum of 45 seconds (the job usually takes about 20–30 seconds) and the idle timeout to 1 second. I sent three requests, with the last one being sent after the first job was completed. However, after 57 seconds, the last request timed out.
I checked the logs, and no workers picked it up, yet I can see that my serverless billing charged me for the last request as well.
We are going live in two weeks, and it's crucial to ensure that we are not charged for requests that were never processed. Any insights on why this might be happening and how to prevent it?
11 replies
RRunPod
•Created by vesper on 1/22/2025 in #⚡｜serverless
How do I calculate the cost of my last execution on a serverless GPU?
For example if I have one GPU with cost $0.00016 and the other ones with $0.00019. How do I know which serverless GPU actually picked this GPU after the request has been completed? Also, is there an easy way to just get the cost of the last
runsync request instead of manually calculating it?3 replies