On Sun, Aug 06, 2006 at 02:03:24PM -0400, Shawn Pearce wrote: > > - It expects an estimated object count as its second parameter. > In your case this would be something around 760000. This tells > it how large of an object table to allocate, with each entry > being 24 bytes + 1 pointer (28 or 32 bytes). Overshooting > this number will cause it to degrade by allocating one > overflow entry at a time from malloc. Hrm, you're allocating a big table and then assigning consecutive entries out of it, as pointers. Why not just malloc a big block, and assign offsets into it, as if it were a really big array. Every time it runs out, realloc it to double the current size, and update the base pointer. -- Ryan Anderson sometimes Pug Majere - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html