public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: <mikedunlavey44@gmail.com>
To: <binutils@sourceware.org>
Subject: feedback on gprofng
Date: Mon, 27 Mar 2023 10:38:44 -0400	[thread overview]
Message-ID: <001a01d960b9$d56bfa60$8043ef20$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

I suggest you have another output from gprofng:

 

(I assume the sampling is on wall-clock time, so it has visibility into
I/O.)

 

Let the user choose a small number N, like 10 or 20, and then select N
stacks at random (with source code line info) and display them, in a tree or
in raw form. The point is - any performance problem consists of activity
that isn't necessary, and if it accounts for fraction F of time, then it
will show up on NF samples. High precision of measurement is not necessary,
but precision of insight is. 

 

If there are multiple threads, let each sample be from all running threads
at the same time, so the user can see which threads are waiting for which
other threads at the point in time.

 

Let me know if this makes sense, or maybe you've already done it.

 

Thanks,

Mike Dunlavey

 

P.S. I've been advocating this for years on StackOverflow. People who've
tried it agree that it works. I've also got a YouTube video about it.

 


             reply	other threads:[~2023-03-27 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 14:38 mikedunlavey44 [this message]
2023-03-27 19:04 ` Ruud van der Pas
2023-03-30 12:23   ` mikedunlavey44
     [not found]     ` <05CC91CC-6095-4DD9-83E3-0A1DC2A5E4D9@oracle.com>
     [not found]       ` <004b01d9631b$4e9a4460$ebcecd20$@gmail.com>
2023-03-30 18:05         ` Ruud van der Pas

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='001a01d960b9$d56bfa60$8043ef20$@gmail.com' \
    --to=mikedunlavey44@gmail.com \
    --cc=binutils@sourceware.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).