News for hackers. Stuff that matters.
Re:Should small Rust structs be passed by-copy or by-borrow? by heyiforgotmypwd on Monday August 26, 2019 @08:24AM (#20799219)
0. Generously use black_box

1. a large sample size

2. a single thread

3. high-precision monotonic timestamps on an unloaded system

4. mean/std dev from more than several runs

Re:Should small Rust structs be passed by-copy or by-borrow? by Groxx on Monday August 26, 2019 @03:26PM (#20802869)
5. run them long enough to stabilize thermally so you don't have bursts of performance (potentially minutes), and/or use something like perflock to lock down your cpu speed: https://github.com/aclements/perflock (general tactic, this is just the last tool I heard of)

6. for similar reasons, run them in a random order each time

Re:Should small Rust structs be passed by-copy or by-borrow? by malkia on Monday August 26, 2019 @12:55PM (#20801455)
Or frameworks helping you do so - like "benchmark" for C++ (though I wonder if there is a cross-language one - that does the same amount of "pre"-warming, same counters, etc.)

Probably not... and too much to ask.