map del efficiency python2.2 and 2.1

[John Hunter]

>>>>> "Tim" == Tim Peters <tim.one at comcast.net> writes:

    Tim> This is exactly the kind of "seemingly random disaster" we
    Tim> see when the platform free() goes nuts, although it's usually
    Tim> much more pronounced than a measly factor of 2.  If so,
    Tim> rebuilding with pymalloc is likely to fix it, while if you
    Tim> don't you'll never answer "why?" without a deep understanding
    Tim> of your platform C's implementation of free().

pymalloc to the rescue.  I rebuilt 2.2 --with-pymalloc and the
interminable delay was vanquished.  

Now where do I go to get a deep understanding of my platform's (glibc
2.2.2) implementation of free and why it behaves so badly?

Thanks for the help
John Hunter