Performance Testing with Voron OMG

note, the numbers are in millions of writes per second here!

for random writes, the numbers are in thousands of writes per second:

okay, i lied about no commentary. what you can see is that in our test, inserting 1.5 million items to storage. in sequential runs, we get such big variance because the test run itself is so short. (nitpicker, yes, we’ll post longer benchmarks).

note that this was running on a pretty good ssd drive, but what about hdd? yes, that isn’t a mistake, esent is doing 901 writes per second.

as we have seen, we are pretty good at reading, but what are the current results?

as you can see, we are significantly better than esent for reads in single and dual threaded modes, but esent is faster when it can use more threads.

that annoyed me, so i set out to figure out what was blocking us. as it turned out, searching the b-tree was quite expensive, but when i added a very small optimization (remember the last few searched pages), we saw something very interesting).

(the esent results are different than the previous run because we run it on a different disk (still ssd)).

what about random reads?

now, one area where we currently suck is large writes, where we are doing really bad, but we’re working on that.

overall, i am pretty happy about it all.