You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For this comparison I built both compilers from source using the tip of their Git repos as of this past Tuesday night.
For SBCL I'm using commit 92951c6f4 and for LuaJIT I'm using b025b01c5b.
I'm not familiar with the LuaJIT build process, so I used the default build procedure, and ran "make" and then "sudo
make install".
For SBCL I built with the following features turned on: (:sb-show-assem :immobile-space :compact-instance-header
:sb-thread :sb-futex :sb-xref-for-internals). I compiled and installed with "make.sh --dynamic-space-size=8192" and
then "sudo sh install.sh"
For the LuaJIT program I'm using the fastest Lua code from the benchmark site with no changes.
The fastest Lisp code uses SBCL's assembly intrinsics, so I used the second fastest program. I modified it to take a
thread count argument and also tweaked the build flags to create an executable instead of a core.
Test Procedure
I created two shell scripts (run_lua.sh and run_lisp.sh) to run the benchmark. Images of size 10000 and 20000 were
generated using 4 and 8 threads, and each run was repeated 8 times.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters