Our Carbon daemon (in graphite) takes up no more than 9% of the processor on a dual-core machine. However, our Graphite webapp has recently raised its HTTPD usage rate to around 95%. From this, we noted that the "wsgi: graphite" process takes up to 93% of the CPU.
Has anyone encountered this problem? What is the solution? We have many control scripts requesting graphite through the graphical URL / Render API. This, of course, will increase the activity of Graphite HTTPD, but we have not made any major changes.
I would appreciate your comments.
source
share