Closed icefoxen closed 4 years ago
I'd quite like to do this, it's a useful metric and something I've been focused on in my own projects. I haven't looked into measuring compile and link time at all so don't have any ideas on how to do it yet.
On Fri., 1 Nov. 2019, 06:32 icefoxen, notifications@github.com wrote:
This may be out of scope for this project but it would be interesting to see how long it takes to compile equivalent code using these various crates. Not sure about the best way to measure though, since rustc's self-benchmarking tools are generally nightly only.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitshifter/mathbench-rs/issues/13?email_source=notifications&email_token=AABBEFC43VWUZ67NEWPGYHDQRMXDLA5CNFSM4JHRC6F2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HV4ZVFA, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABBEFH5EY2Z4JLVPUVM2O3QRMXDLANCNFSM4JHRC6FQ .
I don't either, to be honest, besides doing time cargo build
and collecting the results or such.
Possibly hyperfine would be a good tool for benching compile times, might be overkill though.
There's also the performance monitoring framework for rust itself that might be good for getting some ideas https://github.com/rust-lang-nursery/rustc-perf
This nightly feature should do the job, just need to parse the json output
cargo +nightly build --release -Z timings=html,info,json
This may be out of scope for this project but it would be interesting to see how long it takes to compile equivalent code using these various crates. Not sure about the best way to measure though, since rustc's self-benchmarking tools are generally nightly only.