From e74122b512073e77693827860dd51360af65b20e Mon Sep 17 00:00:00 2001 From: Zygo Blaxell Date: Sun, 11 Nov 2018 13:14:03 -0500 Subject: [PATCH] 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 --- src/bees-resolve.cc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/bees-resolve.cc b/src/bees-resolve.cc index 1a9c548..0634005 100644 --- a/src/bees-resolve.cc +++ b/src/bees-resolve.cc @@ -161,9 +161,11 @@ BeesResolver::adjust_offset(const BeesFileRange &haystack, const BeesBlockData & // Found the hash but not the data. Yay! m_found_hash = true; +#if 0 BEESLOGINFO("HASH COLLISION\n" << "\tneedle " << needle << "\n" << "\tstraw " << straw); +#endif BEESCOUNT(hash_collision); // Ran out of offsets to try