From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: gdb index performance
Date: Wed, 23 Jun 2010 21:08:00 -0000 [thread overview]
Message-ID: <20100623210802.GA17835@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3aaqlbkmx.fsf@fleche.redhat.com>
On Wed, 23 Jun 2010 21:43:02 +0200, Tom Tromey wrote:
> I also did the same tests, but including "thread apply all bt full".
Wasn't there a problem with incomplete backtraces (due to prelink) such as
shown at the top of:
http://sourceware.org/ml/gdb-patches/2010-06/msg00515.html
> The warm cache "bt" results are particularly good (actually I thought
> something went wrong so I did this again by hand -- it really is that
> fast)
Just to be sure - assuming the machine had enough RAM. # of CPUs?
"cold" on SSD storage could hopefully be more like "warm".
(i do not have SSD here.)
Thanks,
Jan
next prev parent reply other threads:[~2010-06-23 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 19:43 Tom Tromey
2010-06-23 21:08 ` Jan Kratochvil [this message]
2010-06-23 21:24 ` Tom Tromey
2010-06-25 16: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=20100623210802.GA17835@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).