Add a timer so we can see what takes a long time to search

Open petdance opened this issue 12 years ago • 3 comments

I'm running the new 2.0 on a big code repo, and I think it is dragging on certain files that 1.x skipped. I'm wondering what they would be.

What if we had a --profiling or --timer mode that would tell me which files were being ack hogs? This is on a file-by-file basis, not profiling like under Devel::NYTProf (which we still need to do).

Apr 19 '13 20:04 petdance

Apr 19 '13 20:04 hoelzro

I think this will help in diagnosing beyondgrep/ack2#236

Apr 20 '13 16:04 petdance

:+1:

Aug 14 '13 14:08 azawawi