Jim et al, > I see that Judy has implemented bottleneck functions in > src/JudyCommon/ in the files JudyMalloc.c and JudyMallocIF.c. It > appears that primary intent of of this implementation is for debugging > and statistics. Has any thought been put into extending Judy's > control over memory allocation so that each Judy array (or set) could > be attached to a memory pool?
Actually we put a LOT of development time into libJudy having its own memory allocator (directly calling sbrk(), etc). We studied the issue deeply. As you might know, malloc() and free() are about the only external requirements used by libJudy -- maybe one more, I forget what it was. Doug decided that there was no gain in having our own memory allocator, compared to a quality implementation of malloc(). It's been eight years and I'm having trouble recalling the public domain version he found and liked best. Doug Lea Malloc maybe? As for memory pools -- not sure what you mean. I haven't kept up. Are there modern malloc() libraries that offer some kind of namespace/pool feature? Does this buy you any performance? Cheers, Alan Silverstein ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
