Benchmarks I've written during development both professionally and during Open Source contributions.
- Java 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
SethFalco
ccd8fa8987
All checks were successful
ci/woodpecker/manual/ci Pipeline was successful
This is just noise which I used to do because I thought it was cool. And it kind of still is, but all platforms show the success status in the latest commit anyway so it's redundant. |
||
| .woodpecker | ||
| config/checkstyle | ||
| gradle/wrapper | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| build.gradle | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
| settings.gradle | ||
Java Microbenchmarks
The motivation and structure of this repository is almost identical to my Node.js equivalent. Read the README of Node.js Microbenchmarks for context.
Running Benchmarks
To see a list of microbenchmarks available, either:
- Look in
src/jmh/fun/falco/microbenchmarks/. - Or execute
./gradlew jmhon its own, which will list them for you.
Run the relevant benchmark with Gradle:
./gradlew jmh --rerun -Pbenchmark=CssToJavaColor
Related
I've written a similar repository for Node.js microbenchmarks: