From: Junio C Hamano <gitster@pobox.com>
To: Karsten Blees <karsten.blees@gmail.com>
Cc: Git List <git@vger.kernel.org>,
msysGit <msysgit@googlegroups.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH v5 10/11] trace: add trace_performance facility to debug performance issues
Date: Tue, 17 Jun 2014 10:11:33 -0700 [thread overview]
Message-ID: <xmqqsin3mpfe.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53980CD8.5090801@gmail.com> (Karsten Blees's message of "Wed, 11 Jun 2014 10:01:28 +0200")
Karsten Blees <karsten.blees@gmail.com> 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 code section to measure */
> start = trace_performance_since(start, "first foobar");
> /* second code section to measure */
> trace_performance_since(start, "second foobar");
>
> Complex use case (measure repetitive code sections):
>
> uint64_t t = 0;
> for (;;) {
> /* ignore */
> t -= getnanotime();
> /* code section to measure */
> t += getnanotime();
> /* ignore */
> }
> trace_performance(t, "frotz");
Hmph. Even though trace_performance() makes an extra call to
getnanotime() in order to return, examples do not use the returned
value? The second example is a good illustration why it makes sense
for trace_performance_since(), though.
> +static void trace_performance_vfl(const char *file, int line,
> + uint64_t nanos, const char *format,
> + va_list ap)
> +{
Just being curious, but what does "v" stand for?
The "_fl" suffix you gave to printf family made a lot of sense to
me, and I would have expected that this to be called with a "_flt"
suffix, meaning "we have file, line and then time as extra
parameters" or something.
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-06-17 17:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 7:55 [PATCH v5 00/11] add performance tracing facility Karsten Blees
2014-06-11 7:56 ` [PATCH v5 01/11] trace: move trace declarations from cache.h to new trace.h Karsten Blees
2014-06-11 7:57 ` [PATCH v5 02/11] trace: consistently name the format parameter Karsten Blees
2014-06-11 7:57 ` [PATCH v5 03/11] trace: remove redundant printf format attribute Karsten Blees
2014-06-11 7:58 ` [PATCH v5 04/11] trace: factor out printing to the trace file Karsten Blees
2014-06-11 7:59 ` [PATCH v5 05/11] trace: add infrastructure to augment trace output with additional info Karsten Blees
2014-06-11 7:59 ` [PATCH v5 06/11] trace: add current timestamp to all trace output Karsten Blees
2014-06-11 8:00 ` [PATCH v5 07/11] trace: move code around, in preparation to file:line output Karsten Blees
2014-06-11 8:00 ` [PATCH v5 08/11] trace: add 'file:line' to all trace output Karsten Blees
2014-06-11 8:01 ` [PATCH v5 09/11] trace: add high resolution timer function to debug performance issues Karsten Blees
2014-06-11 8:12 ` Karsten Blees
2014-06-17 16:44 ` Junio C Hamano
2014-06-18 15:14 ` Karsten Blees
2014-06-11 8:01 ` [PATCH v5 10/11] trace: add trace_performance facility " Karsten Blees
2014-06-17 17:11 ` Junio C Hamano [this message]
2014-06-18 15:14 ` Karsten Blees
2014-06-18 17:28 ` Junio C Hamano
2014-06-11 8:02 ` [PATCH v5 11/11] git: add performance tracing for git's main() function to debug scripts Karsten Blees
2014-06-12 18:30 ` [PATCH v5 00/11] add performance tracing facility Junio C Hamano
2014-06-18 15:14 ` Karsten Blees
2014-06-25 14:28 ` Duy Nguyen
2014-06-25 14:49 ` Karsten Blees
2014-06-26 1:11 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsin3mpfe.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karsten.blees@gmail.com \
--cc=msysgit@googlegroups.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.