public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17604] Stop demangling ELF symbols, at least by default when we have DWARF
Date: Wed, 19 Nov 2014 19:48:00 -0000	[thread overview]
Message-ID: <bug-17604-4717-Qcv80zdp2E@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17604-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17604

--- Comment #3 from dje at google dot com ---
Additional data.
The memory measurement used here is just gdb's internal one, which uses the brk
line, so take into account fairly large error bars here.
Still, I think the numbers are educational.

With my standard monster benchmark:

Without demangled ELF syms:

(gdb) mt set per on
(gdb) file foo
[...]
Command execution time: 2.530785 (cpu), 3.364821 (wall)
Space used: 241299456 (+237711360 for this command)
#symtabs: 5695 (+5695), #primary symtabs: 86 (+86), #blocks: 1061 (+1061)

With demangled ELF syms:

(gdb) mt set per on
(gdb) file foo
[...]
Command execution time: 11.107160 (cpu), 11.104109 (wall)
Space used: 722186240 (+718598144 for this command)
#symtabs: 5695 (+5695), #primary symtabs: 86 (+86), #blocks: 1061 (+1061)

-> ~480MB increase

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-19 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 23:59 [Bug symtab/17604] New: " dje at google dot com
2014-11-15  0:02 ` [Bug symtab/17604] " dje at google dot com
2014-11-15  0:10 ` dje at google dot com
2014-11-18 15:17 ` gbenson at redhat dot com
2014-11-19 19:48 ` dje at google dot com [this message]
2015-06-19 16:50 ` dje at google dot com

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=bug-17604-4717-Qcv80zdp2E@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).