New question #121579 on Graphite: https://answers.launchpad.net/graphite/+question/121579
I have two clustered centos5.5 x86_64 machines (both 8cpu 2323mhz, 31gb mem, with SAN storage) and am using the most recent 0.9.6 release. My curiousity is if these servers would be able to handle multiple high volume connections (totaling possibly 150,000 metrics/minute)?? Or if a pypeD or message bus solution would better serve my needs. I have read other entries about volume and one mentions that the backend was not designed for such large volume connections while the other states that the carbon-cache would grow in size to accomodate processing. Was the statement about the limitations of the backend and volume specific to eariler versions of graphite, pre 0.9.6? References: https://answers.launchpad.net/graphite/+question/37881 In the answer below you stated that the graphite carbon backend was not designed to do itself is multiplex a large number of high volume client connections. https://answers.launchpad.net/graphite/+question/105233 I've never run out of memory because of this myself. I have some very long running carbon processes that are at about 1G rss, that is a lot of memory but they don't seem to ever need more than that Thanks. -- You received this question notification because you are a member of graphite-dev, which is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
