Some time ago, there was a brief thread about zope on Sun. Does Python 1.5.2 run slower than might be hoped ?
Evidence seems to point that way. Our Enterprise 450 gave this. Zope 2.0.0 binary distribution: Python 1.5.2 (#2, Jul 9 1999, 16:07:49) [GCC 2.8.1] on sunos5 Pystone(1.1) time for 10000 passes = 3.93 This machine benchmarks at 2544.53 pystones/second Python compiled by me: Python 1.5.2 (#5, Nov 5 1999, 11:08:13) [GCC 2.95.1 19990816 (release)] on sunos5 Pystone(1.1) time for 10000 passes = 3.42 This machine benchmarks at 2923.98 pystones/second Another solaris box (smaller than the E450) using egcs: Python 1.5.2 (#2, Sep 15 1999, 10:11:04) [GCC egcs-2.91.66 19990314 (egcs-1.1.2 on sunos5 Pystone(1.1) time for 10000 passes = 3.47 This machine benchmarks at 2881.84 pystones/second So there may be something in
Exhibit one: pystone.py on sun -
Pystone(1.1) time for 10000 passes = 5.57 This machine benchmarks at 1795.33 pystones/second
On the LIntel box it was:
Pystone(1.1) time for 10000 passes = 2.36 This machine benchmarks at 4237.29 pystones/second
[snip]
Is it GCC that makes the sun slower than one might hope ? Anyone ?
It may be, but I'm not really qualified to say...as I've only just got a compiled Python working on our E450 and am loathe to try out different compilers! :) Tone ps my iMac 266MHz scored 4500 pystones..maybe I should take my Mac into work and bring the E450 home?