From 998a3c44fd79eac92c375ec9e755288bc146a279 Mon Sep 17 00:00:00 2001
From: Laurenz <laurmaedje@gmail.com>
Date: Thu, 11 May 2023 11:35:45 +0200
Subject: Remove tracing from cheap functions

Turns out that having tracing enabled on some functions that get called a lot distorts the traces so that their parent stack frames look much more expensive than they actually are.
---
 src/util/mod.rs | 1 -
 1 file changed, 1 deletion(-)

(limited to 'src/util')

diff --git a/src/util/mod.rs b/src/util/mod.rs
index 83ec5961..f96fa55e 100644
--- a/src/util/mod.rs
+++ b/src/util/mod.rs
@@ -34,7 +34,6 @@ where
 }
 
 /// Calculate a 128-bit siphash of a value.
-#[tracing::instrument(skip_all)]
 pub fn hash128<T: Hash + ?Sized>(value: &T) -> u128 {
     let mut state = SipHasher13::new();
     value.hash(&mut state);
-- 
cgit v1.2.3