From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] symbol lookup cache
Date: Mon, 22 Dec 2014 12:48:00 -0000 [thread overview]
Message-ID: <20141222124833.GO12884@adacore.com> (raw)
In-Reply-To: <CAP9bCMTC1tbFMB_6sA6Lmuudc+RRuKvHMn=eRb6Jj6-oXCivsg@mail.gmail.com>
> But, *if* one-size-fits-all *wasn't* working (*1), and I think I can
> reasonably assume we're agreed we're not there yet, then would you
> immediately go the route of providing a user option to allow changing
> the size, or first see if gdb could do better on its own?
>
> ---
> (*1): I'm only suggesting exploring dynamically adjusting the cache
> size (I realize you wrote hash size) *if* the data suggests we need
> it. IMO we're not there yet. But, and here's where the disagreement
> is (AFAICT), *if* we do get there, I'd rather see if gdb could do
> better on its own first, before adding a knob that the user has to
> tweak to get the desired performance.
On that, I don't really have an opinion, at least not yet; and since
I don't see us getting there, I propose we do not decide now :).
--
Joel
next prev parent reply other threads:[~2014-12-22 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 8:23 [RFC] " Doug Evans
2014-12-03 0:50 ` Doug Evans
2014-12-20 7:57 ` [PATCH] " Doug Evans
2014-12-20 8:29 ` Doug Evans
2014-12-20 10:43 ` Eli Zaretskii
2014-12-20 19:14 ` Doug Evans
2014-12-20 19:55 ` Eli Zaretskii
2014-12-20 21:04 ` Doug Evans
2014-12-21 3:34 ` Eli Zaretskii
2014-12-21 18:51 ` Doug Evans
2014-12-21 21:01 ` Joel Brobecker
2014-12-22 2:04 ` Doug Evans
2014-12-22 12:48 ` Joel Brobecker [this message]
2015-01-11 19:11 ` Doug Evans
2014-12-03 2:46 ` [RFC] " Joel Brobecker
2014-12-04 16:38 ` Pedro Alves
2014-12-04 19:17 ` Doug Evans
2014-12-04 19:16 ` Jan Kratochvil
2014-12-04 19:24 ` Doug Evans
2014-12-04 19:28 ` Jan Kratochvil
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=20141222124833.GO12884@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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