This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author flub
Recipients BreamoreBoy, flub, loewis, neologix, pitrou, sable, tim.peters
Date 2011-04-26.19:16:10
SpamBayes Score 2.6287245e-10
Marked as misclassified No
Message-id <BANLkTimL2Sei36=xqky6FwyLZ9o9eR80Jw@mail.gmail.com>
In-reply-to <BANLkTinGgGdVr0J7KjrAF4hpKtnffgop_A@mail.gmail.com>
Content
> > So by using dlmalloc on SunOS and AIX you would get the same level
> > of performance for memory operations that you already probably can
> > appreciate on Linux systems.
>
> Yes, but with the above "trick", you can do that without patching
> python nor your app.
> I mean, if you start embedding malloc in python, why stop there, and
> not embed the whole glibc ;-)
> Note that I realize this won't solve the problem for other AIX users
> (if there are any left :-), but since this patch doesn't seem to be
> gaining adhesion, I'm just proposing an alternative that I find
> cleaner, simpler and easier to maintain.

This trick is hard to find however and I don't think it serves Solaris
and AIX users very much (and sadly IBM keeps pushing AIX so yes it's
used more then I like :-( ).

So how about a --with-dlmalloc=path/to/dlmalloc.c?  This way the
dlmalloc code does not live inside Python and doesn't need to be
maintained by python.  But python still supports the code and will
easily be built using it.  Add a note in the README for AIX and
Solaris and I think this would be a lot friendlier to users.  This is
similar in how python uses e.g. openssl to provide optional extra
functionality/performance.
History
Date User Action Args
2011-04-26 19:16:11flubsetrecipients: + flub, tim.peters, loewis, pitrou, sable, neologix, BreamoreBoy
2011-04-26 19:16:10flublinkissue3526 messages
2011-04-26 19:16:10flubcreate