git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v5 09/11] trace: add high resolution timer function to debug performance issues

From
Karsten Blees <karsten.blees@gmail.com>
Date
Jun 18, 2014, 15:14 UTC
Message-ID
<53A1ACD7.1040504@gmail.com>
In-Reply-To
<xmqq4mzjo58t.fsf@gitster.dls.corp.google.com>
Am 17.06.2014 18:44, schrieb Junio C Hamano:
Show 13 quoted lines
> Karsten Blees <karsten.blees@gmail.com> writes:
> 
>> Am 11.06.2014 10:01, schrieb Karsten Blees:
>>> the epoch allows using the results (div 10e9) with other time-related APIs.
>>
>> s/10e9/1e9/
> 
> That replacement is fine but the "(div 1e9)" still wants to be
> clarified.  What did you exactly mean by that?  If the result is
> divided by 10^9 then it yields the number of seconds?
> 
> Thanks.
> 
Div 10^9 yields a time_t. But as not all time-related APIs use time_t, perhaps its best to drop the "(div 1e9)" altogether. That the function returns nanoseconds should be clear enough. Will drop in the next round.
-- 
-- 
*** 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.
Previous: Junio C HamanoNext: Karsten Blees
Message 13 of 23 in “add performance tracing facility”
  1. 00/11 add performance tracing facilityKarsten Blees, Jun 11, 2014
  2. 01/11 trace: move trace declarations from cache.h to new trace.hKarsten Blees, Jun 11, 2014
  3. 02/11 trace: consistently name the format parameterKarsten Blees, Jun 11, 2014
  4. 03/11 trace: remove redundant printf format attributeKarsten Blees, Jun 11, 2014
  5. 04/11 trace: factor out printing to the trace fileKarsten Blees, Jun 11, 2014
  6. 05/11 trace: add infrastructure to augment trace output with additional infoKarsten Blees, Jun 11, 2014
  7. 06/11 trace: add current timestamp to all trace outputKarsten Blees, Jun 11, 2014
  8. 07/11 trace: move code around, in preparation to file:line outputKarsten Blees, Jun 11, 2014
  9. 08/11 trace: add 'file:line' to all trace outputKarsten Blees, Jun 11, 2014
  10. 09/11 trace: add high resolution timer function to debug performance issuesKarsten Blees, Jun 11, 2014
  11. Karsten BleesJun 11, 2014
  12. Junio C HamanoJun 17, 2014
  13. Karsten BleesJun 18, 2014
  14. 10/11 trace: add trace_performance facility to debug performance issuesKarsten Blees, Jun 11, 2014
  15. Junio C HamanoJun 17, 2014
  16. Karsten BleesJun 18, 2014
  17. Junio C HamanoJun 18, 2014
  18. 11/11 git: add performance tracing for git's main() function to debug scriptsKarsten Blees, Jun 11, 2014
  19. Junio C HamanoJun 12, 2014
  20. Karsten BleesJun 18, 2014
  21. Duy NguyenJun 25, 2014
  22. Karsten BleesJun 25, 2014
  23. Duy NguyenJun 26, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.