# Metrics For Temporal Performance Testing

**URL:** <https://community.temporal.io/t/metrics-for-temporal-performance-testing/17026>\
**Category:** Server Deployment\
**Tags:** java-sdk, activity, metrics, testing, web-ui\
**Created:** [April 2, 2025, 10:01am UTC](https://community.temporal.io/t/metrics-for-temporal-performance-testing/17026 "2025-04-02T10:01:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Veeresh](https://avatars.discourse-cdn.com/v4/letter/v/df705f/32.png) [@Veeresh](https://community.temporal.io/u/Veeresh)\
**Post date:** [April 2, 2025, 10:01am UTC](https://community.temporal.io/t/metrics-for-temporal-performance-testing/17026/1 "2025-04-02T10:01:50Z")

</div>

Hi All,

I am setting up performance testing for my Temporal application and need guidance on selecting the right metrics. I followed this Temporal blog → [Scaling Temporal: The Basics | Temporal](https://temporal.io/blog/scaling-temporal-the-basics) on scaling, but I am not seeing similar metrics since I am running Temporal in a Docker-based on-prem setup.

For my testing, I plan to run hundreds of dummy workflows to analyze their behavior. While I have worker metrics being emitted from java sdk which run on “/actuator/prometheus”, I am struggling to identify the key metrics that effectively measure performance. Like from the scaling document it is mentioned that " state\_transition\_count\_count" which I am unable to find, which helps me to understand the performance.

Are there specific metrics I should focus on for performance testing when done from java-sdk? Additionally, is there anything I need to configure differently to get a more accurate measurement of my Temporal application’s performance?

Let me know if any info required from my end.

---

<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:** [April 2, 2025, 2:24pm UTC](https://community.temporal.io/t/metrics-for-temporal-performance-testing/17026/2 "2025-04-02T14:24:28Z")

</div>

Are you testing against on-prem cluster or Temporal Cloud?  
For on-prem cluster you would measure state transitions per second, info on that and other important server metrics are in presentation [here](https://docs.google.com/presentation/d/e/2PACX-1vRAmF1NQjf6Zno6cp0VHfNGFn_XjDDcV46g9xcz-nwrUqqFJUTm1oOORIxJv7B3Bpxpdi2R6CMKncq6/pub?start=false&loop=false&delayms=3000) if it helps.

From worker metrics you would be looking at temporal\_workflow\_task\_scheduled\_to\_start\_latency, temporal\_activity\_schedule\_to\_start\_latency foremost  
but also can share graphs for  
temporal\_sticky\_cache\_size, temporal\_worker\_task\_slots\_available, temporal\_request\_failure, temporal\_long\_request\_failure and your worker pod cpu and memory utilization (in % of max if possible).