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/2001-January/012420.html below:

Python 2.1 slower than 2.0)

[Python-Dev] Benchmarking "fun" (was Re: Python 2.1 slower than 2.0) [Python-Dev] Benchmarking "fun" (was Re: Python 2.1 slower than 2.0)M.-A. Lemburg mal@lemburg.com
Wed, 31 Jan 2001 23:24:43 +0100
Tim Peters wrote:
> 
> [Michael Hudson]
> > ...
> > Can anyone try this on Windows?  Seeing as windows malloc
> > reputedly sucks, maybe the differences would be bigger.
> 
> No time now (pymalloc is a non-starter for 2.1).  Was tried in the past on
> Windows.  Helped significantly.  Unclear how much was simply due to
> exploiting the global interpreter lock, though.  "Windows" is also a
> multiheaded beast (e.g., NT has very different memory performance
> characteristics than 95).

We're still in alpha, no ?  

Adding pymalloc is not much of
a deal since it fits nicely with the Python malloc macros and
giving the package a nice spin by putting it into a Python alpha
release would sure create more confidence in this nice piece
of work. We can always take it out again before going into the 
beta phase.

Or do we have a 2.1 feature freeze already ?

-- 
Marc-Andre Lemburg
______________________________________________________________________
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/



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