Add a results site: does the advice hold on your Ruby? by JuanVqz · Pull Request #250 · fastruby/fast-ruby · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
93 changes: 93 additions & 0 deletions .github/workflows/benchmarks.yml
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,4 @@
*.bundle
/Gemfile.lock
/results/
/_site/
10 changes: 10 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,16 @@ it ran on:
RESULTS_DIR=results RESULTS_LABEL=ruby_3.4 docker compose run --rm ruby_3.4 code/your-new/entry.rb
```

To see those results the way the results site shows them, build the site
into `_site/`, then open `_site/index.html` in a browser:

```
docker compose run --rm -T --entrypoint ruby ruby_4.0 script/build_results_site.rb results _site
```

CI does the same after every run: the site is attached to the run as the
`site-preview` artifact, and published to GitHub Pages from `main`.

## Benchmarks that need a newer Ruby

CI runs every benchmark on every Ruby in `compose.yaml`, back to Ruby 2.1, and
Expand Down
179 changes: 179 additions & 0 deletions script/build_results_site.rb
Loading
Loading