3 ms·
Unsure if OP is the maintainer, but a quick point: Benchmarks without any indication of underlying hardware don't convey a huge amount of information.
by andrewchoi 12y ago
Unsure if OP is the maintainer, but a quick point: Benchmarks without any indication of underlying hardware don't convey a huge amount of information.
- rakoo 12y agoI think the most important thing is to compare with other known dbs on the same hardware, though.
- kasey_junk 12y agoNot really. Different hardware constraints can make serious differences in performance metrics. Some systems perform better on high memory systems and low hd speed, others are the opposite.
- reidrac 12y agoI was thinking almost the same, but to be fair that benchmark is useful to see how different operations compare (eg, delete is 29 times slower than read).
- louischatriot 12y agoYep, also missing on what collection sizes benchmarks are performed. If that's on a 1 doc, 10 docs or 10k docs collections the results are going to be very different. With these kidns of results I expect the dataset size to be quite small. Also benchmarks should be runnable by users :)
- couchand 12y agoTo be fair, it is in the repo, under the /benchmark folder. But don't go look at them, it will make you sad.