You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
On my low loaded server the most of time scout_realtime is in top of CPU consuming processes. I believe it makes sense to add an option to collect the statistics data only when there are connected clients to reduce CPU usage.
The text was updated successfully, but these errors were encountered:
if the last request to /stats.json is older than some threshold (say, 10 seconds), don't run the collectors (or make the collector runs null-ops)
we'd probably want to keep the collectors running for a few minutes after startup, so you still see fully populated charts your first pageview after starting the agent.
One open question is what to do with the historical metrics when the collectors are paused. The collectors use a RingBuffer to store 60 trailing values from each metric (via https://github.com/scoutapp/scout_realtime/blob/master/lib/scout_realtime/lib/aggregator.rb). If you just stop collecting data, the contents of the RingBuffer will still be there when you start again, which will display old data in the charts when you revisit the page.
On my low loaded server the most of time scout_realtime is in top of CPU consuming processes. I believe it makes sense to add an option to collect the statistics data only when there are connected clients to reduce CPU usage.
The text was updated successfully, but these errors were encountered: