A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2006-August/068304.html below:

[Python-Dev] Type of range object members

[Python-Dev] Type of range object members [Python-Dev] Type of range object members"Martin v. Löwis" martin at v.loewis.de
Wed Aug 16 17:29:37 CEST 2006
skip at pobox.com schrieb:
>     Guido> I worry that dropping the special allocator will be too slow.
> 
>     Greg> Surely there's some compromise that would allow recently-used ints
>     Greg> to be kept around, but reclaimed if memory becomes low?
> 
>     Martin> Hardly. The efficiency of the special-case allocator also comes
>     Martin> from the fact that it doesn't ever have to release memory. Just
>     Martin> try changing it to see what I mean.
> 
> Wouldn't use of obmalloc offset much of that?  Before obmalloc was
> available, the int free list was a huge win.  Is it likely to be such a huge
> win today?

That's my theory: it isn't a huge win. Guido has another theory: it's
still faster. Only benchmarking can tell.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4