Terry Reedy wrote:
> I took a look. The only thing that puzzles me is 'warp factor', which
> appears exactly once.
It's been put there via time machine in connection
with the dilithium crystal support in that will be
added in Python 7.0. You don't need to worry about
it yet.
--
Greg
__
"M.-A. Lemburg" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> FWIW: The docs are currently in the README file in Tools/pybench.
I took a look. The only thing that puzzles me is 'warp factor', which
appears exactly once.
tjr
___
Py
M.-A. Lemburg wrote:
> M.-A. Lemburg wrote:
>> Tim Peters wrote:
>>> [M.-A. Lemburg]
I could contribute pybench to the Tools/ directory if that
makes a difference:
>>> +1. It's frequently used and nice work. Besides, then we could
>>> easily fiddle the tests to make Python look better ;
M.-A. Lemburg wrote:
> Tim Peters wrote:
>> [M.-A. Lemburg]
>>> I could contribute pybench to the Tools/ directory if that
>>> makes a difference:
>> +1. It's frequently used and nice work. Besides, then we could
>> easily fiddle the tests to make Python look better ;-)
>
> That's a good argumen
Tim Peters wrote:
> [M.-A. Lemburg]
>> I could contribute pybench to the Tools/ directory if that
>> makes a difference:
>
> +1. It's frequently used and nice work. Besides, then we could
> easily fiddle the tests to make Python look better ;-)
That's a good argument :-)
Note that the tests ar
[M.-A. Lemburg]
> I could contribute pybench to the Tools/ directory if that
> makes a difference:
+1. It's frequently used and nice work. Besides, then we could
easily fiddle the tests to make Python look better ;-)
___
Python-Dev mailing list
Python-
M.-A. Lemburg wrote:
>I could contribute pybench to the Tools/ directory if that
>makes a difference:
>
>
>
+1 on adding pybench.
And we already have parrotbench in the sandbox.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.o
On 4/18/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> Anthony Baxter wrote:
> > On Thursday 06 April 2006 04:10, Benji York wrote:
> >> On a related note: it might be nice to put a pystone run in the
> >> buildbot so it'd be easier to compare pystones across different
> >> releases, different arch
Anthony Baxter wrote:
> On Thursday 06 April 2006 04:10, Benji York wrote:
>> On a related note: it might be nice to put a pystone run in the
>> buildbot so it'd be easier to compare pystones across different
>> releases, different architectures, and between particular changes
>> to the code. (That
On Thursday 06 April 2006 04:10, Benji York wrote:
> On a related note: it might be nice to put a pystone run in the
> buildbot so it'd be easier to compare pystones across different
> releases, different architectures, and between particular changes
> to the code. (That's assuming that the machine
> Benchmarking is hard, let's go shopping!
Quick reminder: pystone is mostly useful for predicting Python's relative
performance across various machines and operating systems. For benchmarking
Python itself, pystone is a seriously impaired tool. For one, it exercises
only
a tiny subset of t
Jeff Epler wrote:
> I'm not trivially able to try a 32-bit build, but for my system it
> appears that 2.5 is moderately faster than 2.4 when built with all the
> defaults.
OK, this prompted me to question my sanity.
Being on a laptop the default is to do frequency scaling (different
speeds depen
I compiled 2.4 and 2.5 from svn. The machine is Fedora Core 4, AMD64.
I built both with
./configure && make
(which gives a "64-bit" binary) and then ran pystone with 20
iterations 10 times:
for i in `seq 1 10`; do ./python Lib/test/pystone.py 20 ; done
The machine was "near idle"
> I still haven't figured out how to mutually lock out builders that are
> on the same slave. This is a frequent thing to happen, as people often
> check-in trunk and backported branch patches nearly simultaneously
> (which is fine, of course - the machines just have to cater with that).
You can t
Neal Norwitz wrote:
> 32-bit or 64-bit? I would expect a modest diff on 64-bit between 2.4 and 2.5.
32-bit; don't know of any 64-bit Pentium Ms :)
> You built both HEAD and 2.4 from scratch, right?
Right.
--
Benji York
___
Python-Dev mailing list
Pyth
On 4/5/06, Benji York <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> > What operating system and compiler?
>
> Oops, should have included that:
> Ubuntu Breezy, Kernel 2.6.12-10-686
> GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
32-bit or 64-bit? I would expect a modes
FYI, on my WinXP box, there appears to be about a 1% pystone difference:
best seen for 2.4.3: 48118.9
best seen for trunk: 47629.8
While tiny, the difference "looked real", as many runs on 2.4.3 broke
48000 but none did on the trunk.
Note that pystone uses wall-clock time on Windows (with
sub-
Benji York wrote:
> I was thinking of "active" branches that there are buildbot slaves
> dedicated to (2.4 at the moment) and the trunk, but (as I mentioned)
> non-idleness pretty much kills that idea. I wonder if the slaves that
> are known to be dedicated to running buildbot and nothing else cou
Martin v. Löwis wrote:
> What operating system and compiler?
Oops, should have included that:
Ubuntu Breezy, Kernel 2.6.12-10-686
GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
> It won't do it across different
> releases, because we don't have Python binaries for each release
Benji York wrote:
> Realizing that early releases don't normally perform as well as final
> releases, I ran pystone for 2.5a1 and compared with 2.4.2 (what I had
> handy). 2.5a1 got slightly more than 30k, while 2.4.2 gets slightly
> more than 35k (1.4 GHz, Pentium M, 1 Meg L2 cache).
What ope
On 4/5/06, Benji York <[EMAIL PROTECTED]> wrote:
> Realizing that early releases don't normally perform as well as final
> releases, I ran pystone for 2.5a1 and compared with 2.4.2 (what I had
> handy). 2.5a1 got slightly more than 30k, while 2.4.2 gets slightly
> more than 35k (1.4 GHz, Pentium M
21 matches
Mail list logo
