# Improving Temporal cluster performance

**URL:** <https://community.temporal.io/t/improving-temporal-cluster-performance/6525>\
**Category:** Server Deployment\
**Tags:** go-sdk, aws, scylla, kubernetes\
**Created:** [November 18, 2022, 6:50am UTC](https://community.temporal.io/t/improving-temporal-cluster-performance/6525 "2022-11-18T06:50:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [November 21, 2022, 1:57pm UTC](https://community.temporal.io/t/improving-temporal-cluster-performance/6525/2 "2022-11-21T13:57:04Z")

</div>

What’s the memory utilization look like on your history pods? Shards are distributed across your history pods and you typically don’t want more than 1K per history host, so would increase replicas if possible.

For server metrics to look into, would start with info in [this](https://community.temporal.io/t/how-to-observe-the-temporal-cluster/5129/3) forum post, note you also need to look at sdk metrics (see forum post [here](https://community.temporal.io/t/suggested-metrics-to-autoscale-temporal-workers-on/5870/3) for more info) because performance tuning involves both your server as well as workers that you deploy and run your code.

Hope this gets you started in right direction.

---

_[View the full topic](https://community.temporal.io/t/improving-temporal-cluster-performance/6525)._