secondbit/pastry — pull request #8 by edsrzf (2012-11-05 09:42:50+00:00)
Title: Make table benchmarks more regular

* Only initialize the benchmark routing table once, lazily

* Don't stop and start the timer in the benchmark loop. The other
work being done is fairly negligible. Stopping and starting the
timer in the loop causes those overheads to be included anyway.

* Use pseudo-random node IDs for consistent results. There's a
fair chance it's faster than crypto/rand too.

* Stop using time for table insert benchmark since it results in
worst-case performance (though average case performance is still
very slow)