Warming up [Billing]
Hello everyone,
I'm curious about the runpod billing on serverless endpoints. Specifically, does runpod charge for elapsed seconds when executing tasks outside the handler? In my use case, I'm concerned about potential charges during tasks such as 'warming up models.' which are not triggered via api, Can anyone provide insights or details on this matter?
Thank you!
Solution:Jump to solution
Yep, you are basically charged from the moment the container starts until the moment it stops, regardless of what it is actually doing or whether the handler has started or not.
2 Replies
cold-start is charged, thats part of what happens outside of handler, e.g. loading models
Solution
Yep, you are basically charged from the moment the container starts until the moment it stops, regardless of what it is actually doing or whether the handler has started or not.