From 28e7ade3fb36d4c8f75ae693acd31c7f32544581 Mon Sep 17 00:00:00 2001 From: Andrew Kelley Date: Fri, 30 Aug 2024 12:54:47 -0700 Subject: [PATCH] more accurate comparison with hyperfine Thanks to David Peter for stopping by! closes #52 --- README.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 6361e60..a50bee9 100644 --- a/README.md +++ b/README.md @@ -39,12 +39,14 @@ However, poop does report peak memory usage as well as 5 other hardware counters, which I personally find useful when doing performance testing. Hey, maybe it will inspire the Hyperfine maintainers to add the extra data points! -Poop does not run the commands in a shell. This has the upside of not -including shell spawning noise in the data points collected, and the downside -of not supporting strings inside the commands. - -Poop treats the first command as a reference and the subsequent ones -relative to it, giving the user the choice of the meaning of the coloring of -the deltas. Hyperfine always prints the wall-clock-fastest command first. +Poop does not support running the commands in a shell. This has the upside of +not including shell spawning noise in the data points collected, and the +downside of not supporting strings inside the commands. Hyperfine by default +runs the commands in a shell, with command line options to disable this. + +Poop treats the first command as a reference and the subsequent ones relative +to it, giving the user the choice of the meaning of the coloring of the deltas. +Hyperfine by default prints the wall-clock-fastest command first, with a command +line option to select a different reference command explicitly. While Hyperfine is cross-platform, Poop is Linux-only.