1
0
mirror of https://github.com/Zygo/bees.git synced 2025-05-17 21:35:45 +02:00

resolver: don't log hash collision incidents

The log message is quite CPU-intensive to generate, and some data sets
have enough hash collisions to throw off benchmarks.

Keep the event counter but drop the log message.

Signed-off-by: Zygo Blaxell <bees@furryterror.org>
This commit is contained in:
Zygo Blaxell 2018-11-11 13:14:03 -05:00
parent 0d5c018c3c
commit e74122b512

View File

@ -161,9 +161,11 @@ BeesResolver::adjust_offset(const BeesFileRange &haystack, const BeesBlockData &
// Found the hash but not the data. Yay! // Found the hash but not the data. Yay!
m_found_hash = true; m_found_hash = true;
#if 0
BEESLOGINFO("HASH COLLISION\n" BEESLOGINFO("HASH COLLISION\n"
<< "\tneedle " << needle << "\n" << "\tneedle " << needle << "\n"
<< "\tstraw " << straw); << "\tstraw " << straw);
#endif
BEESCOUNT(hash_collision); BEESCOUNT(hash_collision);
// Ran out of offsets to try // Ran out of offsets to try