Scott Cheloha <scottchel...@gmail.com> wrote: > > On Jan 24, 2019, at 06:19, Lauri Tirkkonen <loth...@iki.fi> wrote: > > > > [...] > > > > I haven't done any actual measurements though, so it's possible my > > reading is wrong. > > Is there a "grepbench" or canonical corpus we can use to get a 95% > CI on this and future changes? People talk about grep(1) perf. like > CPU time and memory use, there ought to be something better than > "let's search the Linux kernel source for a string that isn't there."
A study of call patterns with ltrace might help