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 gdb/17764] Excessive seeking when reading debug data pegs the CPU @100%
Date: Sat, 27 Dec 2014 16:21:00 -0000 [thread overview]
Message-ID: <bug-17764-4717-9BIpUk7vxu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17764-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17764
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #2 from dje at google dot com ---
Yeah. All those seeks are annoying, but are they really the main cause of the
slow down?
Also, I wouldn't say the non-.gdb_index case is not supportable.
It *is* going to be slower, but if there are fixable perf issues we may fix
them
(emphasis on "may").
If the cpu is pegged at 100% and in this case debug info reading is cpu bound
and not disk bound, how big is the shared library?
If it is relatively big, .gdb_index is definitely the way to go if you want a
speedup.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-27 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 15:46 [Bug gdb/17764] New: " mrsam@courier-mta.com
2014-12-27 15:52 ` [Bug gdb/17764] " jan.kratochvil at redhat dot com
2014-12-27 16:21 ` dje at google dot com [this message]
2014-12-27 17:09 ` mrsam@courier-mta.com
2014-12-27 17:43 ` dje at google dot com
2014-12-27 18:27 ` mrsam@courier-mta.com
2014-12-27 18:44 ` jan.kratochvil at redhat dot com
2014-12-27 18:45 ` jan.kratochvil at redhat dot com
2014-12-28 0:08 ` mrsam@courier-mta.com
2014-12-28 14:40 ` jan.kratochvil at redhat dot com
2014-12-29 15:53 ` hjl.tools at gmail dot com
2014-12-29 23:43 ` mrsam@courier-mta.com
2014-12-29 23:53 ` hjl.tools at gmail dot com
2014-12-30 1:23 ` mrsam@courier-mta.com
2014-12-30 16:27 ` hjl.tools at gmail 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-17764-4717-9BIpUk7vxu@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).