bug#21763: poor performance since grep 2.19 when comparing files with grep

2015-10-27 Thread Bennett, Steve
> Thank you for reporting that. > Interesting: that progression (time vs. increasing N) is clearly quadratic > or worse when using a multibyte locale, but is linear with LC_ALL=C. > I suspect when you run "locale", it reports something like en_US.utf8. Yes, it's a UTF8 locale. I hadn't thought of

bug#21763: poor performance since grep 2.19 when comparing files with grep

2015-10-26 Thread Norihiro Tanaka
On Mon, 26 Oct 2015 11:39:54 -0700 Jim Meyering wrote: > On Mon, Oct 26, 2015 at 5:54 AM, Bennett, Steve > wrote: > > Apologies in advance if this is more of a "discuss" question, but it looks > > like a particular use-case shows a marked change in performance between > > recent versions of g

bug#21763: poor performance since grep 2.19 when comparing files with grep

2015-10-26 Thread Jim Meyering
On Mon, Oct 26, 2015 at 5:54 AM, Bennett, Steve wrote: > Apologies in advance if this is more of a "discuss" question, but it looks > like a particular use-case shows a marked change in performance between > recent versions of grep. > > A colleague mentioned a performance issue with grep to me,

bug#21763: poor performance since grep 2.19 when comparing files with grep

2015-10-26 Thread Bennett, Steve
Apologies in advance if this is more of a "discuss" question, but it looks like a particular use-case shows a marked change in performance between recent versions of grep. A colleague mentioned a performance issue with grep to me, and its puzzling me a bit. It turns out that he was using "grep