-
Notifications
You must be signed in to change notification settings - Fork 1
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
Running ecraven's benchmarks #11
Comments
Sounds excellent. That benchmark suite is impressive but haven't had time to try and run it. Do you know how to hook it up to our containers? |
It seems straight forward to run the tests with docker. I will look into it. |
After cloning the benchmark repository, change directory inside it then: % docker run -it --mount type=bind,source="$(pwd)",target=/benchmark schemers/chibi bash
$ cd /benchmark/
$ ./bench chibi all
Testing browse under Chibi
Including prelude /benchmark/src/Chibi-prelude.scm
Including postlude /benchmark/src/Chibi-postlude.scm
Compiling...
chibi_comp /tmp/larcenous/Chibi/browse.scm /tmp/larcenous/Chibi/browse.scm
Running...
WARNING: importing undefined variable: chibi-version
Running browse:2000
... |
That is the idea. I tried chicken first, but it seems like the docker container is missing the command |
Almost all of our containers should install the Scheme implementation under |
That is exactly the case. |
Bind mounts are one way, or you can do Most of the containers are based on debian, so |
Based on my investigations, we need to fork the benchmarks to adapt it. What do you think @ecraven? |
Based on my investigations, we need to fork the benchmarks to adapt it.
What do you think @ecraven?
I've been planning to containerise things for a long time, but haven't
had the time. I've also started work on a chibi scheme test runner, that
correctly captures compilation time, stdout, stderr, and so on, but that
isn't close to finishing either. I won't be able to finish these
projects anytime soon, so feel free to give it a go.
One thing to keep in mind is that containers *do* have a performance
hit, so there will be people who think that benchmarks run inside a
container are worse than those run on bare metal ;)
Greetings, Peter
|
What about porting ecraven's benchmarks and run them using the containers found in this project so that it is easy for anyone to reproduce the results?
The text was updated successfully, but these errors were encountered: