# Coordinator performance

**URL:** <https://forums.foundationdb.org/t/coordinator-performance/5048>\
**Category:** Using FoundationDB\
**Created:** [August 22, 2025, 3:40pm UTC](https://forums.foundationdb.org/t/coordinator-performance/5048 "2025-08-22T15:40:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![evkuzin](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/evkuzin/32/2027_2.png) [@evkuzin](https://forums.foundationdb.org/u/evkuzin)\
**Post date:** [August 22, 2025, 3:40pm UTC](https://forums.foundationdb.org/t/coordinator-performance/5048/1 "2025-08-22T15:40:19Z")

</div>

Hi folks!  
I’m running fdb cluster on 30 servers, 96 cpu/workers each. I noticed that quite a lot of time coordinator worker is pegged at 100% cpu and after profiling I see the `ClusterGetStatusActor` is consuming the majority of CPU cycles

Multiple concurrent calls to latestEventOnWorkers() for different event types:

MachineMetrics

ProcessMetrics

NetworkMetrics

TraceFileOpenError

ProgramStart

etc..

I noticed that it can be tuned with server knobs like status\_min\_time\_between\_requests, but there are no recommendations (Or I might be reading documentation wrong)

So the question is - what would be the recommendation?

---

<div class="post-metadata">

**Author:** ![gxglass](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/gxglass/32/2003_2.png) [@gxglass](https://forums.foundationdb.org/u/gxglass)\
**Post date:** [August 24, 2025, 1:18am UTC](https://forums.foundationdb.org/t/coordinator-performance/5048/2 "2025-08-24T01:18:47Z")

</div>

No great recommendation (from me, anyway). AI found this, where we document O(500) cores/processes: [Known Limitations — FoundationDB ON documentation](https://apple.github.io/foundationdb/known-limitations.html?utm_source=chatgpt.com)

That said if you can provide a more detailed profile maybe there is something we can do here.