# Recommended metrics to use for autoscaling temporal server pods

**URL:** <https://community.temporal.io/t/recommended-metrics-to-use-for-autoscaling-temporal-server-pods/8079>\
**Category:** Community Support\
**Created:** [April 28, 2023, 8:57pm UTC](https://community.temporal.io/t/recommended-metrics-to-use-for-autoscaling-temporal-server-pods/8079 "2023-04-28T20:57:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwang97](https://avatars.discourse-cdn.com/v4/letter/j/f17d59/32.png) [@jwang97](https://community.temporal.io/u/jwang97)\
**Post date:** [April 28, 2023, 8:57pm UTC](https://community.temporal.io/t/recommended-metrics-to-use-for-autoscaling-temporal-server-pods/8079/1 "2023-04-28T20:57:54Z")

</div>

Currently, we are just scaling off of CPU. Still, we were wondering if there are any official recommendations on what metrics to best scale the various deployments of the temporal server.

Seems like `task_schedule_to_start_latency` would be a reasonable candidate.

---

<div class="post-metadata">

**Author:** ![sushil\_singh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/sushil_singh/32/3712_2.png) [@sushil\_singh](https://community.temporal.io/u/sushil_singh)\
**Post date:** [May 4, 2023, 1:06am UTC](https://community.temporal.io/t/recommended-metrics-to-use-for-autoscaling-temporal-server-pods/8079/2 "2023-05-04T01:06:08Z")

</div>

`task_schedule_to_start_latency` is useful for scaling temporal workers. But you have to look at other 3 servers as well (history, frontend and matching) servers. Scaling those servers should be based on CPU and memory like you would scale any horizontally scaled service