public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [delayed-symfile] [commit] Fix a regression on delayed retrieving of the unwinding debug info.
Date: Wed, 25 Feb 2009 01:47:00 -0000	[thread overview]
Message-ID: <m3vdqzi8yf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090224231429.GC23254@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed\, 25 Feb 2009 00\:14\:29 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> Disputable is whether the delayed reading of partial symtabs and
Jan> unwind info should not be split in half and read separately on
Jan> their specific demand.  Assuming their current load together has
Jan> been decided for the GDB code simplicity and it has no real
Jan> performance impact.

It might not be as deep as that.  Maybe nobody ever looked at this
idea before :-)

I occasionally think that in the future we will end up redoing all the
symbol table and dwarf parsing stuff to be much more incremental.  But
I think this is probably still a lower priority than fixing all the
C++ problems.  And, maybe we'll never really feel the need, I don't
know.

[ type lookup patch ]
Jan> Assuming (did not measure it so far) this patch will nullify any
Jan> performance effect of this archer-tromey-delayed-symfile branch.

I think we'll still see decent benefits in some scenarios.

My canonical test case concerns two things: first, "attach"
performance, and second, "bt" performance.  I do this by running OO.o
Writer (with all debuginfo installed) and then attaching to it; then I
run "thread apply all bt full".

The "attach" part shows us the biggest benefit; I think your patch
won't affect that.  The second thing helps quantify the slowdown
during a typical operation; it also lets us see whether incremental
reading is really working; that is, if you do both of these things
with -batch, you can measure performance gained by not reading some
objfiles.

I'm still interested to hear your results.


I'm very happy that you fixed these bugs, but I also wanted to address
a couple process things here.

I know you have limited time to work on your own major patches, so if
you find bugs like this, feel free to just push them back to the
branch author for fixing.  It is ok to do this publicly.  If the
branch author can't get to the bug in a timely way, we can work
something out.

It is also ok by me if you also want to just fix the bugs like you did
this time.  I just want to make sure that you don't feel trapped into
doing this.


The other process thing is that I obviously made a mess of this
branch.  I must have not run the test suite, or something careless
like that.  I think we need to go back to our original plan of patch
review for everybody.  Let's discuss exactly how to do this, and when
in the process.

Tom

  reply	other threads:[~2009-02-25  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 23:14 Jan Kratochvil
2009-02-25  1:47 ` Tom Tromey [this message]
2009-02-25 14:47   ` Jan Kratochvil
2009-02-25 16:11   ` Jan Kratochvil
2010-07-14 20:32 ` [delayed-symfile] [commit] Fix a regression on CFI without DIE [Re: [delayed-symfile] [commit] Fix a regression on delayed retrieving of the unwinding debug info.] Jan Kratochvil
2010-07-14 21:20   ` Tom Tromey

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=m3vdqzi8yf.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.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).