From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 2/4] dwarf2_physname
Date: Thu, 17 Dec 2009 20:19:00 -0000 [thread overview]
Message-ID: <m38wd1gxp6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B2692EE.5090807@redhat.com> (Keith Seitz's message of "Mon, 14 Dec 2009 11:33:02 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> Okay, so I have some performance numbers for my box using CVS HEAD
Keith> patched and unpatched with my dwarf2_physname patches.
Thanks.
It looks to me like dwarf2_physname is not significantly slower in the
normal (attach and bt) cases -- only in the -readnow case.
Keith> dwarf2_realname:
Keith> real 774m37.623s
On irc Keith suggested that this may be due to swapping.
I probably wouldn't have let this test finish, myself :-)
Keith> As you can see, --readnow (and by extrapolation "info func" and
Keith> "info type") take an enormous performance hit.
I am not concerned about this. I don't think -readnow is actually used
-- I can't imagine why anyone would want to use it. And, on a big
program, an unrestricted "info func" or "info type" is probably just a
mistake, like hitting enter too soon.
I think we should wait a bit to see if there are other comments,
particularly because I imagine a lot of people are going on vacation
soon.
Tom
next prev parent reply other threads:[~2009-12-17 20:19 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:20 Keith Seitz
2009-11-20 22:10 ` Daniel Jacobowitz
2009-11-21 0:04 ` Tom Tromey
2009-11-21 3:46 ` Frank Ch. Eigler
2009-11-23 18:06 ` Tom Tromey
2009-11-23 19:00 ` Daniel Jacobowitz
2009-11-23 16:52 ` Keith Seitz
2009-11-23 17:08 ` Daniel Jacobowitz
2009-11-24 19:20 ` Sami Wagiaalla
2010-01-27 17:10 ` Sami Wagiaalla
2009-12-08 19:47 ` Keith Seitz
2009-12-14 19:33 ` Keith Seitz
2009-12-17 20:19 ` Tom Tromey [this message]
2009-12-17 20:28 ` Daniel Jacobowitz
2009-12-17 22:39 ` Paul Pluzhnikov
2009-12-22 18:35 ` Tom Tromey
2009-12-22 19:24 ` Daniel Jacobowitz
2010-01-20 20:37 ` Keith Seitz
2010-01-26 21:17 ` Daniel Jacobowitz
2010-01-27 19:12 ` Keith Seitz
2010-01-28 20:22 ` Keith Seitz
2010-01-28 20:24 ` Daniel Jacobowitz
2010-01-28 23:41 ` Keith Seitz
2010-02-01 16:48 ` Daniel Jacobowitz
2010-02-01 19:32 ` Keith Seitz
2010-02-01 19:39 ` Daniel Jacobowitz
2010-02-01 21:52 ` Keith Seitz
2010-02-01 22:19 ` Daniel Jacobowitz
2010-02-02 23:23 ` Keith Seitz
2010-02-02 23:31 ` Keith Seitz
2010-02-03 2:46 ` Daniel Jacobowitz
2010-02-04 17:48 ` Tom Tromey
2010-02-04 18:14 ` Daniel Jacobowitz
2010-02-05 17:13 ` Keith Seitz
2010-02-05 17:29 ` Daniel Jacobowitz
2010-02-05 20:24 ` Keith Seitz
2010-02-05 20:57 ` Daniel Jacobowitz
2010-02-05 23:10 ` Keith Seitz
2010-02-05 23:46 ` Daniel Jacobowitz
2010-02-04 17:21 ` Tom Tromey
2010-02-04 17:25 ` Daniel Jacobowitz
2009-11-23 7:31 ` André Pönitz
2009-11-23 16:57 ` Keith Seitz
2009-11-23 17:20 ` Tom Tromey
2009-11-24 7:22 ` André Pönitz
2009-11-24 22:54 ` Tom Tromey
2009-11-25 9:16 ` André Pönitz
2009-11-25 18:14 ` Tom Tromey
2009-11-23 17:15 ` Tom Tromey
2009-11-24 22:11 ` Joel Brobecker
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=m38wd1gxp6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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