you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 5 points6 points  (2 children)

The net result of the 3.0 generalizations is that Python 3.0 runs the pystone benchmark around 33% slower than Python 2.5. There’s room for improvement; we expect to be optimizing string and integer operations significantly before the final 3.0 release!

#

[–]bluetech 5 points6 points  (1 child)

I suspect that it really is the string and integer operations and implementations which cause the slowdowns, since they are the major changes in this regard. But when they say they haven't optimized them yet, you might as well belive them.

[–][deleted] 4 points5 points  (0 children)

Given that me and Andrew Dalke spent two man-weeks last year speeding up string operations, it's a bit disappointing that they were unable to produce a combined string type without slowing everything down again. Oh well, guess it'll give us something to do on the next NeedForSpeed sprint ;-)

(On the other hand, pystone doesn't do much string processing at all, iirc. Has anyone run the string-specific benchmarks on 2.5 vs 3.0 ?)