New question #191807 on Graphite: https://answers.launchpad.net/graphite/+question/191807
I read in one of the answers (comment #4 in https://answers.launchpad.net/graphite/+question/170794) that carbon-cache keeps writing to both the first and last block of each .wsp file. This means that it has to keep lseek+read+write to each of these. I'm not very familiar with Python but a quick search tells me that it supports mmap (http://docs.python.org/library/mmap.html). Using mmap(2) could give a huge advantage: 1. No system call (which is expensive). 2. No copying of data between the process user-space and kernel buffers on each read/write What do you say? -- 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
