H
Helmut Jarausch
Hi,
I was somewhat surprised when I ran pystones with python-2.5.2 and
with python-3.0
On my old/slow machine I get
python-2.5.2
from test import pystone
pystone.pystones()
gives (2.73, 18315.018315018315)
python-3.0
from test import pystone
pystone.pystones()
gives (4.2700000000000005, 11709.601873536298)
That's a drop of 36% !
I know that processing unicode is inherently slower,
but still I was surprised that it's so much slower.
Is there any hope Python-3.0 will get faster or
is the main potential for optimizations exhausted, already?
That's not to start a flame war!
I know computers get faster, we human beings don't (me, at least)
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
I was somewhat surprised when I ran pystones with python-2.5.2 and
with python-3.0
On my old/slow machine I get
python-2.5.2
from test import pystone
pystone.pystones()
gives (2.73, 18315.018315018315)
python-3.0
from test import pystone
pystone.pystones()
gives (4.2700000000000005, 11709.601873536298)
That's a drop of 36% !
I know that processing unicode is inherently slower,
but still I was surprised that it's so much slower.
Is there any hope Python-3.0 will get faster or
is the main potential for optimizations exhausted, already?
That's not to start a flame war!
I know computers get faster, we human beings don't (me, at least)
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany