{"push_id":2034283249,"size":2,"distinct_size":2,"ref":"refs/heads/jemalloc","head":"79527c12c22666cbc0a19c94d838888ef7743705","before":"71b605baa9c4939977c62c6cfa1ee625b90db50c","commits":[{"sha":"5fe927d303e32ee3714b3b2c51041a0b80e71e7a","author":{"name":"Alexander Kyte","email":"98c1b9471a6ddb3b22a1b071b7dd7e5b59f3b075@gmail.com"},"message":"[runtime] Bring jemalloc to mono\n\nJemalloc is known to have much better performance than system memory\nallocators, and is safe in concurrent/re-entrant situations.\n\nTo use, provide the following options to configure:\n\n--with-jemalloc to enable optionally. To use at runtime,\nexport MONO_USE_JEMALLOC to the environment.\n\n--with-jemalloc-always to enable and make the default\n\n--with-jemalloc-assert to enable with assertions to catch memory\nunsafety. It adds overhead, but an overhead that's much less than\nvalgrind or asan.\n\nIf you export\nMONO_JEMALLOC_CONF=\"stats_print:true\"\n\nYou will see detailed memory statistics for mono at exit.\n\nNow note that jemalloc is used through an explicit registration, so\nC libraries called through pinvoke calls will not use jemalloc unless\nthey configure themselves to do so separately.\n\nTo understand the build work, I'm statically linking jemalloc.a into\nthe compilation unit for mono/utils/mono-jemalloc.c, which is\nresponsible for registering it with mono at startup. No further\ncopying out of the submodule is necessary at installation time.","distinct":true,"url":"https://api.github.com/repos/alexanderkyte/mono/commits/5fe927d303e32ee3714b3b2c51041a0b80e71e7a"},{"sha":"79527c12c22666cbc0a19c94d838888ef7743705","author":{"name":"Alexander Kyte","email":"98c1b9471a6ddb3b22a1b071b7dd7e5b59f3b075@gmail.com"},"message":"[dontmerge/forjenkins] Always enable jemalloc, so CI builds with enabled for pkg","distinct":true,"url":"https://api.github.com/repos/alexanderkyte/mono/commits/79527c12c22666cbc0a19c94d838888ef7743705"}]}
{"actor":{"display_login":"alexanderkyte"}}