From 6b84e4c712b38f73d3a091dd846c32bfc7d641fd Mon Sep 17 00:00:00 2001 From: Matthew Johnson Date: Wed, 4 Sep 2024 18:22:48 -0400 Subject: [PATCH] spectator-go adjust timing advice Given that high-resolution streaming is gaining more usage, we should only recommend publishing according to the spectatord publish interval. --- docs/spectator/lang/go/usage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/spectator/lang/go/usage.md b/docs/spectator/lang/go/usage.md index 30e66a21..1c1ce300 100644 --- a/docs/spectator/lang/go/usage.md +++ b/docs/spectator/lang/go/usage.md @@ -114,6 +114,6 @@ collection. This client is stateless, and sends a UDP packet (or unixgram) to `spectatord` each time a meter is updated. If you are performing high-volume operations, on the order of tens-of-thousands or millions of operations per second, then you should pre-aggregate your metrics and report them at a cadence -closer to the `spectatord` publish interval of 5 seconds, or the Atlas metrics granularity of 1 minute. -This will keep the CPU usage related to `spectator-go` and `spectatord` low (around 1% or less), as -compared to up to 40% for high-volume scenarios. +closer to the `spectatord` publish interval of 5 seconds. This will keep the CPU usage related to +`spectator-go` and `spectatord` low (around 1% or less), as compared to up to 40% for high-volume +scenarios.