When chasing down performance problems in ack, we're often flying blind. Devel::NYTProf is great, but it almost offers too much data. It would be nice if we could do something like this:
# PROBE: begin resource loop
while ( my $resource = $resources->next ) {
...
}
# PROBE: end resource loop
and provide a custom option to insert time measurement instructions.
The generated code should be inserted by squash, and activated in ack-standalone by a --timings option. We also need to plan for the following:
Being able to activate/deactivate certain probes when running ack
Being able to provide parameters to probes (so we can see how long ack spends doing something on a particular file, for example)
Beings able to get total time for a probe that runs more than once (ex. total amount of time spent analyzing files)
hoelzro
commented
11 years ago
When chasing down performance problems in ack, we're often flying blind.
Devel::NYTProfis great, but it almost offers too much data. It would be nice if we could do something like this:and provide a custom option to insert time measurement instructions.
The generated code should be inserted by
squash, and activated inack-standaloneby a--timingsoption. We also need to plan for the following: