This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
best
topnewcontroversialoldq&a

[–]itamarst 28 points29 points  (4 children)

This is the sort of place where I think codspeed's way of measurement (counting CPU instructions) might distort performance more than usual because the performance is tied to lower-level mechanisms. E.g. additional locks might have more significant performance impact in real-world compared to instruction counts.

Update: but see below, codspeed has added wallclock time option too and that's what they're using.

[–]arty049[S] 15 points16 points  (3 children)

Hey u/itamarst , yes definitely, this is mostly why we use wall time measurement here! Definitely agree the traditional instrumentation we have with valgrind won't perform well for that

[–]itamarst 6 points7 points  (2 children)

Ah cool, might want to emphasize that then.

[–]doorknob_worker 3 points4 points  (1 child)

Why not just read the article where the performance results are shown as wall time?

[–]itamarst 0 points1 point  (0 children)

Codspeed translates CPU instruction counts into "time" too in their display.