mirror of
https://github.com/Zygo/bees.git
synced 2025-05-17 13:25:45 +02:00
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 <bees@furryterror.org>
This commit is contained in:
parent
44810d6df8
commit
e22653e2c6
@ -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
|
||||
----
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user