STINNER Victor <[EMAIL PROTECTED]> added the comment: I'm unable to use pystone nor pybench to compare all integers patches. So I wrote my own tool: bench_int.py. Don't use to compare different computers or Python versions, it's just useful to test if a patch is faster or slower.
Example (still the 64 bits [EMAIL PROTECTED] GHz): ------------------------------- original : 896.5 ms + macros : 891.0 ms (+0.6%) ++ optimize : 884.3 ms (+1.4%) +++ shift : 880.8 ms (+1.7%) GMP : 700.9 ms (+22%) 30 bits : 659.9 ms (+26%) ------------------------------- Result: my optimizations are useless, whereas mark's patch (#4258) is 26% faster! My GMP patch is only 22% faster (and so slower than the 30 bits patch). The GMP hack would only be useful for huge value whereas my benchmark tool use mostly small values (the biggest is near 2**200). I use it with "sync && ./python -OO bench_int.py", run the command 2 or 3 times, and keep the smallest value. Added file: http://bugs.python.org/file11981/bench_int.py _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4294> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
