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

Profiling support?

From
David Kastrup <dak@gnu.org>
Date
Feb 11, 2014, 11:17 UTC
Message-ID
<87d2itc2zv.fsf@fencepost.gnu.org>

Looking in the Makefile, I just find support for coverage reports using gcov. Whatever is there with "profile" in it seems to be for profile-based compilation rather than using gprof.

Now since I've managed to push most of the runtime for basic git-blame operation out of blame.c proper, it becomes important to figure out where most of the remaining runtime (a sizable part of that being system time) is being spent. Loop counts like that provided by gcov (or am I missing something here?) are not helpful for that, I think I rather need the kind of per-function breakdown that gprof provides.

Is there a reason there are no prewired recipes or advice for using gprof on git? Is there a way to get the work done, namely seeing the actual distribution of call times (rather than iterations) using gcov so that this is not necessary?

-- 
David Kastrup
Next: Duy Nguyen
Message 1 of 10 in “Profiling support?”
  1. David KastrupFeb 11, 2014
  2. Duy NguyenFeb 11, 2014
  3. David KastrupFeb 11, 2014
  4. John KeepingFeb 11, 2014
  5. David KastrupFeb 11, 2014
  6. David KastrupFeb 11, 2014
  7. Thomas RastFeb 16, 2014
  8. David KastrupFeb 16, 2014
  9. Thomas RastFeb 16, 2014
  10. David KastrupFeb 16, 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.