startToClose staying constant, scheduleToStart increasing under heavy load

Hello @rich_tweed

However, when there is heavy load with clients calling for many workflows to be run, the startToClose metric increases and the scheduleToStart metric stays near 0

Is this for workflow tasks or activity tasks? could you point to the exact metric here Temporal SDK metrics reference | Temporal Documentation?

Can you check your pods CPU and memory utilization?

should I be using a different metric to determine autoscaling?
For reference, you can have a look at this post
Suggested metrics to autoscale Temporal workers on