# Too high schedule to start latency with fine metrics

**URL:** <https://community.temporal.io/t/too-high-schedule-to-start-latency-with-fine-metrics/11471>\
**Category:** Community Support\
**Tags:** go-sdk, helm, general-impl, activity\
**Created:** [March 22, 2024, 1:31pm UTC](https://community.temporal.io/t/too-high-schedule-to-start-latency-with-fine-metrics/11471 "2024-03-22T13:31:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [March 25, 2024, 7:44pm UTC](https://community.temporal.io/t/too-high-schedule-to-start-latency-with-fine-metrics/11471/3 "2024-03-25T19:44:42Z")

</div>

| but schedule\_to\_start with workflows and activities is too high, over 800ms in average and 1.5s max

from server metrics take a look at

sum(rate(persistence\_requests{operation=“CreateTask”}[1m]))

and share please. Also show from sdk metrics your worker\_task\_slots\_available, filter by worker\_type.

If persistence requests for CreateTask are low and your task slots available for WorkflowWorker/ActivityWorker are not depleted (go to 0 when your schedule to start latencies are high)  
then consider upping workflow and activity task pollers from default 2/2 in Go to possibly 10/10 and see if that makes a difference.

---

_[View the full topic](https://community.temporal.io/t/too-high-schedule-to-start-latency-with-fine-metrics/11471)._