A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-February/076767.html below:

[Python-Dev] int/float freelists vs pymalloc

[Python-Dev] int/float freelists vs pymalloc [Python-Dev] int/float freelists vs pymallocNeal Norwitz nnorwitz at gmail.com
Fri Feb 8 07:01:49 CET 2008
On Feb 7, 2008 5:09 AM, Andrew MacIntyre <andymac at bullseye.apana.org.au> wrote:
>
> So I've been testing with the freelists ripped out and ints and floats
> reverted to fairly standard PyObject_New allocation (retaining the small
> int interning) and thus relying on PyMalloc to do any compaction.
>
> The results have been somewhat surprising...
>
> The short version is that:
> - for ints, the freelist is ahead of PyMalloc by a very small margin
>    (<4%)
> - for floats, the freelist is a long way behind PyMalloc (>35% slower)

Martin did some profiling of ints in py3k 1.5 years ago.  The results
of his profiling are here:
    http://svn.python.org/projects/python/branches/py3k/INTBENCH

I think Martin wrote a mail to describe his work in more detail.  But
the only mails I could find are not what I remember:

  http://mail.python.org/pipermail/python-3000/2006-August/003185.html
  http://mail.python.org/pipermail/python-3000/2006-August/003064.html

I don't remember if he did any work on head or if he remembers any
more that might be relevant here.

n
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