criterion.nim
criterion.nim copied to clipboard
Statistic-driven micro-benchmark framework
Results
2
criterion.nim issues
Sort by
recently updated
recently updated
newest added
Currently it is difficult to isolate setup code from the part of the code that one really wants to measure. Silly example: ```nimrod proc silly(n: int) {.measure: [100, 10000, 1000000].}...
in my own benchmarking lib I'm introducing `preventOptimizeOut` based on `volatileLoad` to: * prevent optimizing out results * have minimum impact on runtime performace * be as simple to use...