RetroSearch Browse

Thu Oct 6 10:44:49 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-October/057008.html

Neal Norwitz <nnorwitz at gmail.com> writes:

> On 10/5/05, Phillip J. Eby <pje at telecommunity.com> wrote:
>> At 09:50 AM 10/4/2005 +0100, Michael Hudson wrote:
>> >(anyone still thinking about removing the block stack?).
>>
>> I'm not any more.  My thought was that it would be good for performance, by
>> reducing the memory allocation overhead for frames enough to allow pymalloc
>> to be used instead of the platform malloc.
>
> I did something similar to reduce the frame size to under 256 bytes
> (don't recall if I made a patch or not) and it had no overall effect
> on perf.

Hey, me too!  I also came to the same conclusion.

Cheers,
mwh

-- 
  The ultimate laziness is not using Perl.  That saves you so much
  work you wouldn't believe it if you had never tried it.
                                        -- Erik Naggum, comp.lang.lisp

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-October/057008.html below:

[Python-Dev] Removing the block stack