Martin v. Löwis wrote:
Is it the
x64 working faster at its design sizes
Another guess (still from the darkness of not having received the
slightest clue what the test actually does): if it creates integers
in range(2**32, 2**64), then they fit into a Python int on AMD64-Linux,
but require a Pyt
...
--
Ran 193 tests in 27.841s
OK
real0m28.150s
user0m26.606s
sys 0m0.917s
[rpt...@localhost tests]$
magical how the total python time is less than the real time.
time(1) also measures the Python startup and
On 2009-02-04 11:14, Robin Becker wrote:
> Martin v. Löwis wrote:
I follow David's guess that Linux does better IO than Windows (not
knowing anything about the benchmark, of course)
>>> I originally thought it must be the vmware host stuff offloading IO to
>>> the second core, but wa
> Is it the
> x64 working faster at its design sizes
Another guess (still from the darkness of not having received the
slightest clue what the test actually does): if it creates integers
in range(2**32, 2**64), then they fit into a Python int on AMD64-Linux,
but require a Python long on 32-bit Win
On Feb 4, 10:14 am, Robin Becker wrote:
> > [rpt...@localhost tests]$ time python25 runAll.py
> > .
>
> .
>
> > --
> > Ran 193 tests in 27.841s
>
Martin v. Löwis wrote:
I follow David's guess that Linux does better IO than Windows (not
knowing anything about the benchmark, of course)
I originally thought it must be the vmware host stuff offloading IO to
the second core, but watching with sysinternals didn't show a lot of
extra stuff goin
>> I follow David's guess that Linux does better IO than Windows (not
>> knowing anything about the benchmark, of course)
>>
> I originally thought it must be the vmware host stuff offloading IO to
> the second core, but watching with sysinternals didn't show a lot of
> extra stuff going on with th
Martin v. Löwis wrote:
.
I follow David's guess that Linux does better IO than Windows (not
knowing anything about the benchmark, of course)
Regards,
Martin
I originally thought it must be the vmware host stuff offloading IO to
the second core, but watching with sysinternals didn't show a
Tim Daneliuk wrote:
..
Which vmware product?
vmware server
--
Robin Becker
--
http://mail.python.org/mailman/listinfo/python-list
Paul Rubin wrote:
Robin Becker writes:
so it looks like the vmware emulated system is much faster. Is it the
x64 working faster at its design sizes or perhaps the compiler or
could it be the vmware system caching all writes etc etc? For the red
hat x64 build the only special configuration was t
Diez B. Roggisch wrote:
Robin Becker schrieb:
Whilst doing some portability testing with reportlab I noticed a
strange speedup for our unittest suite with python2.5
host win32 xp3 unittest time=42.2 seconds
vmware RHEL x64 unittest time=30.9 seconds
so it looks like the vmware emulated syste
Robin Becker writes:
> so it looks like the vmware emulated system is much faster. Is it the
> x64 working faster at its design sizes or perhaps the compiler or
> could it be the vmware system caching all writes etc etc? For the red
> hat x64 build the only special configuration was to use ucs2
Y
Robin Becker schrieb:
Whilst doing some portability testing with reportlab I noticed a strange
speedup for our unittest suite with python2.5
host win32 xp3 unittest time=42.2 seconds
vmware RHEL x64 unittest time=30.9 seconds
so it looks like the vmware emulated system is much faster. Is it t
Robin Becker wrote:
> Whilst doing some portability testing with reportlab I noticed a strange
> speedup for our unittest suite with python2.5
>
> host win32 xp3 unittest time=42.2 seconds
> vmware RHEL x64 unittest time=30.9 seconds
>
> so it looks like the vmware emulated system is much faster
On Wed, Feb 4, 2009 at 2:36 AM, Robin Becker wrote:
> Whilst doing some portability testing with reportlab I noticed a strange
> speedup for our unittest suite with python2.5
>
> host win32 xp3 unittest time=42.2 seconds
> vmware RHEL x64 unittest time=30.9 seconds
>
> so it looks like the vmware
Robin Becker wrote:
> Whilst doing some portability testing with reportlab I noticed a strange
> speedup for our unittest suite with python2.5
>
> host win32 xp3 unittest time=42.2 seconds
> vmware RHEL x64 unittest time=30.9 seconds
>
> so it looks like the vmware emulated system is much faster
Whilst doing some portability testing with reportlab I noticed a strange speedup
for our unittest suite with python2.5
host win32 xp3 unittest time=42.2 seconds
vmware RHEL x64 unittest time=30.9 seconds
so it looks like the vmware emulated system is much faster. Is it the x64
working faster
17 matches
Mail list logo
