check-hotpath

Detect hot-path allocation violations in Rust code by scanning for risky patterns like Box::new, Vec::new(), String::new(), Arc::new, .clone(), .to_string(), and .to_owned(). The audit flags these issues while allowing exceptions like Vec::with_capacity() at the end of a path.

Holding a lock across an .await boundary in Rust introduces blocking behavior that degrades hot-path performance. The audit flags Mutex::new, RwLock::new, .lock(), .read(), and .write() usage across awaits, encouraging non-blocking or parking_lot primitives instead.

Audit Rust hot-path code for non-deterministic syscalls by detecting Instant::now(), SystemTime::now(), or std::time patterns that introduce timing variance. The audit identifies these violations and recommends using shard-cached timestamps for deterministic execution.

Find zero-copy alternatives in Rust by detecting copy violations like .to_vec(), .to_owned(), and copy_from_slice. The audit advocates using zero-copy alternatives such as Bytes::slice() to eliminate unnecessary memory duplication on hot paths.

You can apply this hot-path audit to specific Rust source directories including src/command/, src/protocol/, src/io/, src/storage/dashtable/, and event loop files. It enforces a zero-tolerance policy by flagging high-severity issues and providing concrete fixes.

Check branch density and nested match arms in Rust code when optimizing hot paths, as excessive cases or nested branches hinder performance. The audit identifies these structural violations to streamline critical execution paths and reduce branching overhead.