Just jotting down some ideas to make that better.
Mostly: simplify it.
[ ] Only one project (Literate and CommonMark can be in the same project, it's okay)
[ ] Only one benchmarking script (it can test everything: both startup latency (TTFParse etc), and full compiled speed)
(Right now it's setup for 'possible future' other benchmarking scripts, but let's be realistic)
Only one .md file? It's nice that github auto-opens the ReadMe when opening the benchmarks folder on GitHub. So maybe that could be the output file generated with Literate.jl from the benchmarking script.\
Or two markdown files (ReadMe.md, benchmark.md), that's fine too
Misc:
[ ] Print now() (yes you can look at commit date, but that's a bit hidden and could be != run date)
Also, maybe:
[ ] add it to CI, to track performance regressions.
You can then flip through the 'History' of the benchmark markdown file on github, to see how timings change
re the
benchmark/dir I introduced in59
Just jotting down some ideas to make that better. Mostly: simplify it.
Misc:
now()(yes you can look at commit date, but that's a bit hidden and could be != run date)Also, maybe: