Hi, While going through the libmicrohttpd sources, I noticed this part in daemon.c:
/* Allocate memory pool in the processing thread so * intensively used memory area is allocated in "good" * (for the thread) memory region. It is important with * NUMA and/or complex cache hierarchy. */ connection->pool = MHD_pool_create (daemon->pool_size); I'm curious why libmicrohttpd is doing its own memory management. If I remember correctyl the memory allocater of glibc has pools of memory per thread? It does keep freed() memory in a per-thread list before it is moved to the global pool of free memory. Regards.