Explore using mmap for data file access

Bug #989427 reported by Michael Leinartas
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
whisper
Confirmed
Wishlist
Unassigned

Bug Description

From question: https://answers.launchpad.net/graphite/+question/191807

Original description:

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 blocks of each .wsp file.
This means that it has to keep doing lseek+read+write system calls every time it updates the file.
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 calls (which are expensive).
2. No copying of data between the process user-space and kernel buffers on each read/write

Changed in graphite:
importance: Undecided → Wishlist
status: New → Confirmed
Sidnei da Silva (sidnei)
affects: graphite → whisper
Revision history for this message
Michael Leinartas (mleinartas) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.