<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1454688547976_60999"><br></div><div>Hi Folks,</div><div id="yui_3_16_0_1_1454688547976_61075"><br></div><div dir="ltr" id="yui_3_16_0_1_1454688547976_61076">Are there any statistics available on the meta-data overhead for using jemalloc? What is the usual percentage of meta-data overhead to user memory - is that number available? Are there any comparisons available - say comparing to other "popular" malloc implementations?</div><div id="yui_3_16_0_1_1454688547976_61097" dir="ltr"><br></div><div id="yui_3_16_0_1_1454688547976_61098" dir="ltr">Is the amount of meta-data tuneable in any way - any compilation flags/configurations?</div><div id="yui_3_16_0_1_1454688547976_61140" dir="ltr"><br>Right now, we are using Jemalloc 3.6, but will be moving to the latest release - is there any difference in the amount of meta-data between those releases?</div><div id="yui_3_16_0_1_1454688547976_61171" dir="ltr"><br></div><div id="yui_3_16_0_1_1454688547976_61172" dir="ltr">Right now, for a general purpose allocator, it looks like the overhead is very much higher than Glibc malloc. We are looking very seriously at jemalloc for some large-scale applications on Linux - in particular, we are interested in the ability of jemalloc to return/unmap memory. But if the overhead is very high, this will be a real problem. Can any guidance be given on the typical overhead?<br></div><div id="yui_3_16_0_1_1454688547976_61196" dir="ltr"><br></div><div id="yui_3_16_0_1_1454688547976_61198" dir="ltr">Thanks//Steve<br></div></div></body></html>