On Sun, Mar 8, 2009 at 4:05 AM, Victor Stinner
wrote:
> I just downloaded Python 2.6.1, 3.0.1 and 3.1alpha1, compiled them on 32 and
> 64 bits CPU, and ran pybench 2.1(*).
>
> Summary (minimum total) on 32 bits CPU:
> * Python 2.6.1: 8762 ms
> * Python 3.0.1: 8977 ms
> * Python 3.1a1: 9228 ms (
Le Sunday 08 March 2009 13:20:34 Antoine Pitrou, vous avez écrit :
> Hi,
>
> Victor Stinner haypocalc.com> writes:
> > Summary (minimum total) on 32 bits CPU:
> > * Python 2.6.1: 8762 ms
> > * Python 3.0.1: 8977 ms
> > * Python 3.1a1: 9228 ms (slower than 3.0)
>
> Have you compiled with or with
On Sun, Mar 8, 2009 at 7:30 AM, Christian Heimes wrote:
> Antoine Pitrou wrote:
>> Hi,
>>
>> Victor Stinner haypocalc.com> writes:
>>> Summary (minimum total) on 32 bits CPU:
>>> * Python 2.6.1: 8762 ms
>>> * Python 3.0.1: 8977 ms
>>> * Python 3.1a1: 9228 ms (slower than 3.0)
>>
>> Have you co
Christian Heimes cheimes.de> writes:
>
> Why is the feature still disabled by default?
Marc-André expressed concerns that it might trigger compiler issues.
> PS: Holy moly! Computed gotos totally put my Python on fire! The feature
> increases the minimum run-time by approx. 25% and the average
Antoine Pitrou wrote:
> Hi,
>
> Victor Stinner haypocalc.com> writes:
>> Summary (minimum total) on 32 bits CPU:
>> * Python 2.6.1: 8762 ms
>> * Python 3.0.1: 8977 ms
>> * Python 3.1a1: 9228 ms (slower than 3.0)
>
> Have you compiled with or without "--with-computed-gotos"?
Why is the featur
Hi,
Victor Stinner haypocalc.com> writes:
>
> Summary (minimum total) on 32 bits CPU:
> * Python 2.6.1: 8762 ms
> * Python 3.0.1: 8977 ms
> * Python 3.1a1: 9228 ms (slower than 3.0)
Have you compiled with or without "--with-computed-gotos"?
Regards
Antoine.
_
Hi,
> So, 3.1 is 30% faster in user CPU time, even though it probably has more
> tests (...)
Wow!
I just downloaded Python 2.6.1, 3.0.1 and 3.1alpha1, compiled them on 32 and
64 bits CPU, and ran pybench 2.1(*).
Summary (minimum total) on 32 bits CPU:
* Python 2.6.1: 8762 ms
* Python 3.0.1:
Antoine Pitrou wrote:
Hello,
Out of curiosity, I timed running the test suite ("./python -m test.regrtest")
in non-debug mode, in both the release30-maint and py3k branches:
* release30-maint got:
302 tests OK.
[...]
165.79user 26.03system 5:01.75elapsed 63%CPU
* py3k got:
304 tests OK.
[...]
Hello,
Out of curiosity, I timed running the test suite ("./python -m test.regrtest")
in non-debug mode, in both the release30-maint and py3k branches:
* release30-maint got:
302 tests OK.
[...]
165.79user 26.03system 5:01.75elapsed 63%CPU
* py3k got:
304 tests OK.
[...]
113.33user 28.93system 4
