Feature #820
closedbufferlist memory pool
0%
Description
Investigate putting buffers in a separate memory pool.
Updated by Sage Weil about 13 years ago
- Target version changed from v0.25 to v0.26
Updated by Greg Farnum about 13 years ago
To elaborate: it appears when I compare the heap memory use reported by massif* and the resident memory usage reported by top that we are continuing to have serious issues with memory fragmentation. tcmalloc improved this situation over ptmalloc but it's still not good enough for people running in RAM-limited situations and our heap usage is low enough that it should allow proper use.
[*] or tcmalloc heap profiler.
Updated by Greg Farnum about 13 years ago
- Status changed from New to In Progress
I did a prototype of this, and in brief testing it reduced resident memory usage a little bit, but not by enough. More experimentation might improve results; but after looking at the test data some and discussing with Sage, #834 definitely comes first!
Updated by Greg Farnum about 13 years ago
- Status changed from In Progress to Closed
So, tried this out and it looked like maybe it helped a little bit, but it wasn't clear. After running more tests with higher tcmalloc output, and examining the proc/maps, it's starting to look like memory use issues aren't actually with the heap but...something else. I don't think this is worth much more looking into.
Updated by Sage Weil about 13 years ago
- Translation missing: en.field_story_points set to 2
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 538