Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: save lots of memory
Date: Sun, 27 Dec 2009 03:40:00 -0000	[thread overview]
Message-ID: <20091227033948.GA6597@adacore.com> (raw)
In-Reply-To: <20091105172839.GI4557@adacore.com>

> I'm looking forward to measuring the impact on memory and performance
> with one of the bigger apps we have in house :-).

I finally took the time to make some measurements.  The app I used has
about 600kSLOCs (with comments, it is a little over a million lines)
of Ada, builds and link to about 145MB of code and 70MB of debug info
making a grand total of 215MB.

    GDB startup time: 3.125s -> 2.369s => delta: -0.756s / -24.1 %
    Peak memory usage: 158.3MB -> 70.9MB => delta: -87.4MB / -55.0 %

    The same, but with -readnow:
    GDB startup time: 7.339s -> 6.461s => delta: 0.878s / - 11.9%
    Peak memory usage: 568.4MB -> 429.5MB => delta: -138.9MB / -24.4 %

Unsurprisingly, symbol lookup time did not appear to be affected either way.

I also quickly tried a patch suggested by Tom (attached), and got worse
results on both startup time and memory usage. No visible effect on lookup
performance. Not sure why, yet. I will keep the idea in mind, though.
For now, I must switch to something else again.

Impressive numbers nonetheless. This is a really nice catch, Tom!
-- 
Joel


  reply	other threads:[~2009-12-27  3:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  1:24 Tom Tromey
2009-11-05 17:28 ` Joel Brobecker
2009-12-27  3:40   ` Joel Brobecker [this message]
2009-11-05 19:59 ` Daniel Jacobowitz
2009-11-06 18:20   ` Tom Tromey
2009-11-06 19:23     ` Paul Pluzhnikov
2009-11-06 20:50       ` Tom Tromey
2009-11-16 18:41     ` Tom Tromey
2009-11-16 22:14       ` 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=20091227033948.GA6597@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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