Karsten Blees writes:
> Right, it makes no sense for trace_performance(), and for
> trace_performance_since() only if followed by another 'measured' code
> section. In that special case, I think it wouldn't hurt if you had to
> write:
>
> uint64_t start = getnanotime();
> /* first code sectio
Am 17.06.2014 19:11, schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> Simple use case (measure one code section):
>>
>> uint64_t start = getnanotime();
>> /* code section to measure */
>> trace_performance_since(start, "foobar");
>>
>> Medium use case (measure consecutive code sections)
Karsten Blees writes:
> Simple use case (measure one code section):
>
> uint64_t start = getnanotime();
> /* code section to measure */
> trace_performance_since(start, "foobar");
>
> Medium use case (measure consecutive code sections):
>
> uint64_t start = getnanotime();
> /* first cod
Add trace_performance and trace_performance_since macros that print a
duration and an optional printf-formatted text to the file specified in
environment variable GIT_TRACE_PERFORMANCE.
These macros, in conjunction with getnanotime(), are intended to simplify
performance measurements from within t
4 matches
Mail list logo
