From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27673] [debuginfod] Handle source requests for same buildid more efficiently
Date: Wed, 31 Mar 2021 15:00:56 +0000 [thread overview]
Message-ID: <bug-27673-10460-HqkSBEZu5v@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27673-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27673
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
The subject line "handle sources ... from same buildid ... more efficiently"
suggests a caching opportunity. The debuginfod --fdcache-prefetch parameter is
probably the gadget of interest here. The opensuse operators could experiment
with a much larger than default figure. (You can test it locally by running
debuinfod for yourself, against a local set of relevant -debug* RPMs.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-31 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 14:45 [Bug debuginfod/27673] New: " vries at gcc dot gnu.org
2021-03-31 14:58 ` [Bug debuginfod/27673] " fche at redhat dot com
2021-03-31 15:00 ` fche at redhat dot com [this message]
2021-03-31 15:33 ` vries at gcc dot gnu.org
2021-03-31 16:03 ` fche at redhat dot com
2021-03-31 16:41 ` vries at gcc dot gnu.org
2021-04-01 6:06 ` vries at gcc dot gnu.org
2021-12-03 21:52 ` fche at redhat dot com
2022-01-19 23:50 ` fche at redhat 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-27673-10460-HqkSBEZu5v@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).