Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compilation doesn't seem to matter, performance-wise, when running pystone.py #2

Closed
deepfire opened this issue Oct 25, 2010 · 2 comments

Comments

@deepfire
Copy link

Roughly:

  • (CLPYTHON:RUN #p"/usr/lib/python2.6/test/pystone.py" :compile nil :args '("pystone.py" "1000000"))
    Pystone(1.1) time for 1000000 passes = 28.630005
    This machine benchmarks at 34928.39 pystones/second
  • (CLPYTHON:RUN #p"/usr/lib/python2.6/test/pystone.py" :compile t :args '("pystone.py" "1000000"))
    Pystone(1.1) time for 1000000 passes = 29.440002
    This machine benchmarks at 33967.387 pystones/second

As a contrast, this machine marks at roughly 90000 pystones with cpython 2.6.

@deepfire
Copy link
Author

I forgot to add, that host Lisp is SBCL 1.0.40.

@metawilm
Copy link
Owner

(Sorry for the delay.)
SBCL is a compile-only implementation:
http://www.sbcl.org/manual/index.html#Compiler_002donly-Implementation
On e.g. Allegro CL compilation makes it run almost 5 times as fast.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants