Hello there. First of all, thanks for that awesome project, I have been using this daily for various tasks.
I'm not even sure if anyone wants this kind of feature but I'm the kind of guy that cares about performance and I like to be able to identify bottlenecks easily.
For that reason, I would like to have the ability to measure execution time (I know that measuring time in a not very granular way such as using CPU timestamp counters is not indicative of actual bottlenecks) in an easy way at least on a recipe level (maybe per line timings would be better but recipe is a good granularity level).
I have already implemented the feature so, if you would like something like that, I can open a PR to merge.
How I have currently implemented that is pretty straightforward:
- pass
-t|--time and just will print the time it takes to execute the recipe and any recipe dependencies of that.
- The output is like so:
<materialized recipe> (Duration: <duration>) which is printed immediately after the recipe is done.
Hello there. First of all, thanks for that awesome project, I have been using this daily for various tasks.
I'm not even sure if anyone wants this kind of feature but I'm the kind of guy that cares about performance and I like to be able to identify bottlenecks easily.
For that reason, I would like to have the ability to measure execution time (I know that measuring time in a not very granular way such as using CPU timestamp counters is not indicative of actual bottlenecks) in an easy way at least on a recipe level (maybe per line timings would be better but recipe is a good granularity level).
I have already implemented the feature so, if you would like something like that, I can open a PR to merge.
How I have currently implemented that is pretty straightforward:
-t|--timeand just will print the time it takes to execute the recipe and any recipe dependencies of that.<materialized recipe> (Duration: <duration>)which is printed immediately after the recipe is done.