Keeping idle workers alive even without any requests.
Hey everyone, does anyone have a clear understanding of how idle timeout works on RunPod?
It seems like billing is based on max workers by default.
For instance on this deployment I set 5 max workers, 0 active workers, and an idle timeout of 5 seconds, but even with no requests, I still see 3 idle workers. Is this expected behavior, or is something off?
It seems like billing is based on max workers by default.
For instance on this deployment I set 5 max workers, 0 active workers, and an idle timeout of 5 seconds, but even with no requests, I still see 3 idle workers. Is this expected behavior, or is something off?
