From 9aaa144f7ae21adb01828351f7f25db35ef888c0 Mon Sep 17 00:00:00 2001 From: Martin Sumner Date: Fri, 11 Aug 2017 11:13:43 +0100 Subject: [PATCH] Major mixup! Got my leveled and leveldb results the wrong way round. --- docs/ANTI_ENTROPY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ANTI_ENTROPY.md b/docs/ANTI_ENTROPY.md index 7b2045f..e28e9c8 100644 --- a/docs/ANTI_ENTROPY.md +++ b/docs/ANTI_ENTROPY.md @@ -130,7 +130,7 @@ There is also a significant cost with AAE. The following chart compares perform ![](pics/BaselineCompare_with2i_AAE.png) -The purple and blue lines sho Riak+leveled throughput with/without AAE enabled, the reg and orange lines show the same for Riak+leveldb. +The purple and blue lines show Riak+leveldb throughput with/without AAE enabled, the reg and orange lines show the same for Riak+leveled. The AAE configuration used in this test was aggressive in terms of AAE tree rebuild (every four hours), but the significant gap in throughput seen with and without AAE persists even during spells in the test when there is no rebuild activity taking place (e.g. 13,000 to 15,000 elapsed seconds). Maintaining an additional key-store strictly for entropy management places a non-trivial cost on throughput of a heavily loaded cluster.