Hello,
quick remark regarding the multi-thread lock/mutex situation in glibc, in
recent version this can be now tuned as well with the MALLOC_ARENA_MAX
environment variable. This way glibc will also maintain multiple memory pool,
but apparently at the cost of a higher memory consumption during
Not the original developer of the memory managers, but, iirc, one of the
reasons for private memory manager was to avoid a multi-threading
related lock/mutex that is done by system malloc()/free(), which is not
necessary for pure multi-process application. I did not analyzed myself,
but I guess
