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

Fixed axis charts

Browse source 
Also compariosn betwen 6 hour and 8 hour tests
This commit is contained in:
martinsumner 2017-02-21 12:10:05 +00:00
parent ede93c5bb6
commit ec021d73e3
7 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/VOLUME.md
View file

@ -111,7 +111,14 @@ The difference in volatility is clear when graphing the test performance:
leveled Results | eleveldb Results
:-------------------------:|:-------------------------:
![](../test/volume/cluster_three/output/summary_leveled_5n_100t_nosync.png "LevelEd") | ![](../test/volume/cluster_three/output/summary_leveldb_5n_100t_nosync.png "LevelDB")
![](../test/volume/cluster_three/output/summary_5n_100t_i2_nosync_leveled.png "LevelEd") | ![](../test/volume/cluster_three/output/summary_5n_100t_i2_nosync_leveldb.png "LevelDB")
Repeating this test over 8 hours with a smaller keyspace and a uniform (not pareto) key distribution yields similar results. This change in test parameters was done to reduce the percentage of not_founds towards the end of the test (down to about 20%).
leveled Results | eleveldb Results
:-------------------------:|:-------------------------:
![](../test/volume/cluster_three/output/summary_5n_100t_i2_nosync_leveled_uniform.png "LevelEd") | ![](../test/volume/cluster_three/output/summary_5n_100t_i2_nosync_leveldb_uniform.png "LevelDB")
### Lies, damned lies etc