| 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.