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
Looks like only a single carbon-cache.py instance is started. I'm starting to experience performance issues with querying graphite, and write timeouts when clients attempt to connect to graphite.
I am running this image on a 4-CPU machine, and if I understand correctly, the best practice is to run one instance of carbon-cache.py per CPU.
Is there a way to do that?
The text was updated successfully, but these errors were encountered:
Nothing baked into the image as of yet, but I like the idea of making this dynamic. Let me know if you take a stab at it; otherwise, I'll see what I can do when I get some time to work on it.
Cactusbone
pushed a commit
to F4-Group/docker-graphite-statsd
that referenced
this issue
Jul 28, 2020
First of all, thanks so much for this project!
Looks like only a single
carbon-cache.py
instance is started. I'm starting to experience performance issues with querying graphite, and write timeouts when clients attempt to connect to graphite.I am running this image on a 4-CPU machine, and if I understand correctly, the best practice is to run one instance of
carbon-cache.py
per CPU.Is there a way to do that?
The text was updated successfully, but these errors were encountered: