Skip to content
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

Backend performance #130

Open
wrossmann opened this issue Nov 21, 2016 · 0 comments
Open

Backend performance #130

wrossmann opened this issue Nov 21, 2016 · 0 comments

Comments

@wrossmann
Copy link

We have a large amount of perfdata we're pushing through to Carbon and I've found that Graphios is capping out at about 7k metrics per second. In order to get through a backlog of perfdata I moved the older data to a separate spool folder and started a second Graphios process which is now happily throwing another 7k metrics per second into my Graphite infra.

For this I would like to raise 2 issues:

  1. In the Carbon backend the socket is set up and torn down each time send() is called. I've observed that this causes a significant amount of overhead while Graphios is processing metrics.
  2. The current single-threaded nature of Graphios is holding it back. I believe that building in the ability to run two or more worker threads within a single instance of Graphios would greatly improve performance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant