From e22653e2c631253635a9db50b37c02cf5d35736b Mon Sep 17 00:00:00 2001 From: Zygo Blaxell Date: Wed, 27 Nov 2024 20:39:09 -0500 Subject: [PATCH] docs: remove "matched_" prefix event counters We can no longer reliably determine the number of hash table matches, since we'll stop counting after the first one. Signed-off-by: Zygo Blaxell --- docs/event-counters.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/event-counters.md b/docs/event-counters.md index a53c5a4..65098c9 100644 --- a/docs/event-counters.md +++ b/docs/event-counters.md @@ -181,16 +181,6 @@ The `hash` event group consists of operations related to the bees hash table. * `hash_insert`: A `(hash, address)` pair was inserted by `BeesHashTable::push_random_hash_addr`. * `hash_lookup`: The hash table was searched for `(hash, address)` pairs matching a given `hash`. -matched -------- - -The `matched` event group consists of events related to matching incoming data blocks against existing hash table entries. - - * `matched_0`: A data block was scanned, hash table entries found, but no matching data blocks on the filesytem located. - * `matched_1_or_more`: A data block was scanned, hash table entries found, and one or more matching data blocks on the filesystem located. - * `matched_2_or_more`: A data block was scanned, hash table entries found, and two or more matching data blocks on the filesystem located. - * `matched_3_or_more`: A data block was scanned, hash table entries found, and three or more matching data blocks on the filesystem located. - open ----