umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

Add result from first hour

Browse source
This commit is contained in:
martinsumner 2017-02-28 21:26:50 +00:00
parent a82ce44255
commit 8482f5acc9
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/VOLUME.md
View file

@ -171,6 +171,6 @@ Riak + leveled | Riak + bitcask
:-------------------------:|:-------------------------: :-------------------------:|:-------------------------:
![](../test/volume/cluster_five/output/summary_leveled_5n_60t_i2_16KB_nosync.png "LevelEd") | ![](../test/volume/cluster_five/output/summary_bitcask_5n_60t_i2_16KB_nosync.png "LevelDB") ![](../test/volume/cluster_five/output/summary_leveled_5n_60t_i2_16KB_nosync.png "LevelEd") | ![](../test/volume/cluster_five/output/summary_bitcask_5n_60t_i2_16KB_nosync.png "LevelDB")
Over the whole test, the bitcask-backed cluster achieves <b>16.48%</b> more throughput than leveled, but in the last hour this advantage is just <b>0.34%</b>. In the first hour of the test, bitcask throughput is <b>39.13%</b> greater than leveled. Over the whole test, the bitcask-backed cluster achieves <b>16.48%</b> more throughput than leveled, but in the last hour this advantage is just <b>0.34%</b>.
The results for bitcask look a bit weird and lumpy though, so perhaps there's something else going on here that's contributing to the gap closing. The results for bitcask look a bit weird and lumpy though, so perhaps there's something else going on here that's contributing to the gap closing.