Hello there. We've been noticing some peak in our p99 latency. We've been trying to identify the cause, but initial checks (CPU, memory, MongoDB latency, etc.) haven't revealed anything. After reading the self-hosted best practices, I suspect the stats engine might be having an impact. The documentation suggests splitting the engine if an impact is observed. However, I'd like to confirm if the stats engine is indeed the source of the issue. Is it possible to monitor it in isolation or something?

p99 for GrowthBook itself?

The

/api/features/:key

endpoint

Hi Sid - the /api/feature endpoint shouldn't be calling the stats, as that end point should just be returning the feature payload

I apologize; I don't think I explained myself clearly enough. We have noticed occasional peaks in the

/api/features

endpoint, but after investigating our infrastructure, we haven't found any clear "aggressors." MongoDB latency, CPU and memory usage, and CPU throttling all appear fine. We are now wondering if the stats engine might be the cause. To confirm this, we need to monitor the stats engine. How can we verify that our suspicion is correct?