From d33e662d6f2a10bc17d76c47d546adf81c72f62c Mon Sep 17 00:00:00 2001 From: Changkun Ou Date: Sat, 1 Jan 2022 15:52:13 +0100 Subject: [PATCH] content: minor text change --- content/posts/bench-time.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/bench-time.md b/content/posts/bench-time.md index 2756261..0f627f4 100644 --- a/content/posts/bench-time.md +++ b/content/posts/bench-time.md @@ -125,7 +125,7 @@ Atomic/n-100000/w/o-timer-8 432µs ± 0% What's interesting in the modified benchmark result is by testing target code with a higher cost, the difference between `with-timer` and `w/o-timer` gets much closer. For instance, in the last pair of output when `n=100000`, the measured atomic operation only has `(444µs-432µs)/100000 = 0.12 ns` difference, which is pretty much accurate other than when `n=1` the error is `(34.8ns-6.44ns)/1 = 28.36 ns`. -So, how is this happening? There are two ways to trace the problem down to the bare bones. +How is this happening? There are two ways to trace the problem down to the bare bones.