-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long ping times #125
Comments
Ford thing to check would be your CPU limits - you might be starving them
for CPU time.
On Fri, 7 Oct 2022 at 06:34, Montana Mendy ***@***.***> wrote:
Hey all,
Saw a similar post with this problem. When I try and install via Helm
chart the default Grafana chart showed very long ping times; circa ~3
seconds for some larger clusters, and even a ten node cluster is showing ~1
to ~2 second ping times.
As one user has done, I made a new build and instrumented out the calls a
bit and the reported time seems accurate, but when I hit the /ping
endpoints directly from pods with other tools like a timed curl the time
seems much more reasonable (~a few mills).
—
Reply to this email directly, view it on GitHub
<#125>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVIOWUZZH7PSPULB3CAVTWB6Y7VANCNFSM6AAAAAAQ7IF2DI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Best regards,
Mikolaj Pawlikowski
+44 747 330 2049
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey all,
Saw a similar post with this problem. When I try and install via Helm chart the default Grafana chart showed very long ping times; circa ~3 seconds for some larger clusters, and even a ten node cluster is showing ~1 to ~2 second ping times.
As one user has done, I made a new build and instrumented out the calls a bit and the reported time seems accurate, but when I hit the
/ping
endpoints directly from pods with other tools like a timedcurl
the time seems much more reasonable (~a few mills).The text was updated successfully, but these errors were encountered: