Re: HOWTO: benchmarking monotone (was Re: [Monotone-devel] "memory exhausted" error for 'mtn list status' command)

[Eric Anderson]

Nathaniel Smith writes:
 > Of course, things are slightly more subtle even than that... I believe
 > massif is looking at
 >   allocated bytes + per currently allocated block overhead + stack size
 >   - freed bytes
 > while memtime is looking at
 >   allocated bytes - large freed blocks - re-used freed bytes
 >   + heap overhead + stack + mmap()'d executable/library size
 > or so?

Indeed, I expect memtime also would could shared mem segments, 
mmaped files, mmaped anonymous pages.

 > I wonder if there's any convenient way to mask off the read-only mmaps
 > from memtime, it would make the numbers easier to interpret (and in
 > particular, make it much easier to compare massif and memtime in order
 > to measure fragmentation; none of these tools measure fragmentation
 > directly).

You could parse /proc/pid/maps and try to do something there. 
        -Eric