public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Lindsay <alexlindsay239@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Noted slowness in profile loading with binutils 2.37
Date: Tue, 8 Feb 2022 10:45:32 -0800	[thread overview]
Message-ID: <CANFcJrGH6h54t5Qxbk429w+82HJKZvFoutFam9y_C4Af0UN_9Q@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrE7D2U68dXXrYmx+ivYY-+Zx+144poniJ_6m+kpGY6ZQ@mail.gmail.com>

Hmm, I'm trying with master and I still see the slowness. I'll note that I
also saw the slowness when I configured a 2.37 build with
`--enable-follow-debug-links=no` when I was wondering if that was the
relevant change.

On Tue, Feb 8, 2022 at 9:58 AM H.J. Lu <hjl.tools@gmail.com> wrote:

> On Tue, Feb 8, 2022 at 9:45 AM Alexander Lindsay via Binutils
> <binutils@sourceware.org> wrote:
> >
> > Hi all,
> >
> > I recently experienced a slow-down in profile loading by the tool pprof,
> > and I believe I've boiled it down to changing from previous versions of
> > binutils to binutils version 2.37. Timings of profile loading are
> > documented on the pprof ticket I originally opened here:
> > https://github.com/google/pprof/issues/680#issuecomment-1032174210. I
> > reproduce them below:
> >
> > - binutils version 2.29.1: 1.1 seconds
> > - binutils version 2.33.1: 1.1 seconds
> > - binutils version 2.35.2: 6.8 seconds
> > - binutils version 2.36.1: 6.5 seconds
> > - binutils version 2.37: Still not loaded at 6 minutes
> >
> > I think the relevant binutil tool here is addr2line. Does anyone have a
> > quick idea for what may have caused the slow-down? I was thinking about
> > doing a git bisect, but I figured it is probably way more efficient to
> > contact the experts!
> >
>
> This may be related to:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28843
>
> --
> H.J.
>

  reply	other threads:[~2022-02-08 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 17:44 Alexander Lindsay
2022-02-08 17:57 ` H.J. Lu
2022-02-08 18:45   ` Alexander Lindsay [this message]
2022-02-09  1:09 ` Alan Modra
2022-02-10 11:00 ` Nick Clifton
2022-02-11 18:16   ` Alexander Lindsay
2022-02-11 18:17     ` Alexander Lindsay
2022-02-14 14:18       ` Nick Clifton

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=CANFcJrGH6h54t5Qxbk429w+82HJKZvFoutFam9y_C4Af0UN_9Q@mail.gmail.com \
    --to=alexlindsay239@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    /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).