• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

bencheeorg / benchee / aeecba5f792caa4a2e4be5af2a8466263ae551c0 / 2
94%
master: 95%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 18 Dec 2023 09:04AM UTC
Files 53
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Dec 2023 09:02AM UTC coverage: 93.843% (-0.4%) from 94.249%
aeecba5f792caa4a2e4be5af2a8466263ae551c0.2

Pull #414

github

PragTob
Introduce `BenchmarkConfig` to selectively use config in benchmark

Fixes #412 - but basically the `Config` holds `inputs` and that
can be a hell loat of data to send along with every benchmark.

In a benchmark with 16 scenarios and huge inputs we now save
ourselves copying that potentially huge data structure a whopping
16 times to our benchmarking processes for no reason whatsoever
(the scenarios already hold the `input`).
Pull Request #414: Introduce `BenchmarkConfig` to selectively use config in benchmark

884 of 942 relevant lines covered (93.84%)

7770.9 hits per line

Source Files on job aeecba5f792caa4a2e4be5af2a8466263ae551c0.2
  • Tree
  • List 0
  • Changed 20
  • Source Changed 0
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 0
  • aeecba5f on github
  • Prev Job for on minimize-benchmark-data (#8c84fb41e89ea80d18a4c9ff8df561dbf21c28ed.1)
  • Next Job for on minimize-benchmark-data (#38eeab318583068e7346538bec508933cc5b3467.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc