From 676bf12dc32c2cd287dc625715dd96e061289ec9 Mon Sep 17 00:00:00 2001 From: Martin Sumner Date: Tue, 1 Aug 2017 13:16:49 +0100 Subject: [PATCH] Add figures on rate of list_keys operations --- docs/ANTI_ENTROPY.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/ANTI_ENTROPY.md b/docs/ANTI_ENTROPY.md index 09c6224..6a1b1e7 100644 --- a/docs/ANTI_ENTROPY.md +++ b/docs/ANTI_ENTROPY.md @@ -323,3 +323,11 @@ Of note is the escalating response times of the fold as the size of the database With leveled there was a strongly favourable comparison, with both improved response times, and less dramatic rises in those times as the database grew. ![](pics/listkeys_jobtime_compare.png) + +Even when using the (constrained) node_worker_pool the leveled implementation runs list_keys jobs at a rate of 155K keys per second. By contrast leveldb runs at 45K keys per second with the vnode_worker_pool and just 16K keys per second when throttled by using the node_worker_pool. + +The intention is though, not to use list_keys operations in AAE - but instead to dynamically produce TicTac Trees either by folding objects (or heads with leveled) or folding over specialist indexes. + +### Phase 2 + +tbc