Originally posted by stormcrow
View Post
In the end (this was some years ago but the strangeness of it made me remember it to this day) I shrugged it off as either a strange anomaly or a flawed benchmark and decided to keep the optimized version since it made no sense that it would be slower. And the slowdown was very tiny, we are talking some microseconds after processing some millions of messages, and the thing that mattered most was that in all my code was 1600% faster than our precious solution (which was itself 145% faster than the fastest Java implementation available on the open market).
I read that the SQLite devs no longer runs any benchmarks regularly since the complexity of todays systems taint the picture (which is why I also cringe when I see these benchmarks on Phoronix where the chart shows "number of nanoseconds" since the difference shown there between the systems are probable below the standard deviation anyway) and instead rely on the cycle count done by Valgrind.
Leave a comment: