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

Question: ideal graphite server configuration for high-volume environments? #379

Closed
lukevenediger opened this issue Aug 1, 2013 · 1 comment

Comments

@lukevenediger
Copy link
Contributor

Hi,

My company's graphite server runs on an ubuntu 12.04 box with two cores and 4gb of RAM, with a SAN volume for storage.

Lately I've had to restart apache at least once a day because the dashboards get stuck waiting for graphs to render, but they never do. After a restart I'm able to load the dashboards quickly. At the same time, volumes on the system are growing and so this problem is only likely to get worse unless I scale it out somehow.

What has worked for you in your organisation? How did you scale your set up to handle increased query load?

Thanks!
Luke

@obfuscurity
Copy link
Member

This really belongs on the mailing list or Launchpad Q&A. There is no one ideal configuration. The best thing you can do is to optimize for IO using SSDs or arrays of very fast disk. From there it just takes standard system engineering practices to identify the bottlenecks and adjust your configuration accordingly.

I have some examples up on obfuscurity/graphite-scripts#4 that may be helpful. We're also planning to document Graphite's clustering capabilities better, you can follow #816 for updates.

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

2 participants