Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFA: shrink minimal symbols
Date: Wed, 27 Aug 2008 22:48:00 -0000	[thread overview]
Message-ID: <m3d4ju2hzt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080827205745.GA10837@caradoc.them.org> (Daniel Jacobowitz's message of "Wed\, 27 Aug 2008 16\:57\:45 -0400")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> The OO.o/firefox numbers are with shared libraries loaded, I assume.

Yeah.

Daniel> Do you have any performance comparison?  I'm not too worried about
Daniel> lookup performance - number of lookups is relatively low though with
Daniel> full debug info I'd expect it to be linear to the number of minimal
Daniel> symbols.  But I am concerned about startup time.

Good point.  It does slow things down a bit :(

I did: 'time gdb -batch-silent' either with a file name or -p $PID:

OO.o before and after
    2.47user 0.29system 0:03.13elapsed 88%CPU
    2.51user 0.30system 0:04.98elapsed 56%CPU

firefox
    0.75user 0.16system 0:00.92elapsed 99%CPU
    0.77user 0.14system 0:00.92elapsed 99%CPU

libgcj
    1.28user 0.10system 0:01.43elapsed 96%CPU
    1.51user 0.09system 0:01.76elapsed 91%CPU

So, back to the drawing board, I think.  Perhaps using two different
types of hash table is in order -- that would keep the space savings
but ameliorate the performance problems, I think.  I'll look a bit
later.

I have another space-savings patch I'm toying with ... I'll time it
before sending it.

Tom


  reply	other threads:[~2008-08-27 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 20:01 Tom Tromey
2008-08-27 20:58 ` Daniel Jacobowitz
2008-08-27 22:48   ` Tom Tromey [this message]
2008-08-28  1:40     ` Daniel Jacobowitz

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=m3d4ju2hzt.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@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