New question #105233 on Graphite: https://answers.launchpad.net/graphite/+question/105233
We have a graphite system that is quite busy, 42k metrics updated every 30 seconds. We plan on adding about 250k metrics although they will not all be updated at 30 seconds. The system is fast enough to handle it, dual Xeon 5500, Raid5 15k drives etc.. When we start our metric loader process intraday it attempts to load the metrics from the beginning of the day as fast as it can. Carbon-cache grows in size as it is busy creating the whisper files, processing incoming data, etc. When carbon-cache catches up, the resident memory size of the process stays at about 1 gig, it never shrinks. Is this the intended behavior of a very busy carbon-cache system? Should we expect the memory footprint to only grow and never shrink? -- 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
