Re: [Valgrind-developers] valgrind/coregrind

[Julian S. <js...@ac...>]

> Changed (client-heap-size : client-map-seg-size) ratio from 3:1 to 1:2.
> As a result, can now mmap much more memory (eg. for Memcheck, 850MB up from
> 250MB, for Nulgrind 1750MB up from 700MB). 

That's good.  However, is tht 850MB all in one lump, or in a lot
of small pieces?  Memcheck gives quite a large overhead per
allocation (100+ bytes?), and I wonder if that has any influence
on the optimal settings?  For stuff like KDE and OpenOffice the
average allocation size is small (50-100 bytes) so perhaps
it's worth adjusting the parameters optimally for that?

J