public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <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 16:41:50 +0000	[thread overview]
Message-ID: <bug-27673-10460-q6Nj8BO4Kh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27673-10460@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Frank Ch. Eigler from comment #4)
> > debuginfod:
> > - when receiving a source request and ENOENT, send as reply the list of
> >   available files for the buildid
> > 
> > client:
> > - when receiving a list of available files for a buildid, store it and
> >   use it to reply to source requests related to the buildid. That is,
> >   if the file is not in the list, reply with -2.  Otherwise, send a
> >   request to debuginfod, and expect it to succeed.
> 
> Interesting.  A more first-class solution could be a new webapi to
> enumerate source files: a "/buildid/HEXCODE/sourcelist" query that
> returns a structured piece of data.  This can be computed by debuginfod
> fairly rapidly.  The client could cache that and use it to drive a
> negative-cache hit on a subsequent source query.

Agreed, it would be good to have this kind of functionality available more
generically.

Then the client (preferably the elfutils client itself using some setting,
otherwise the part using the elfutils client) could upon the first source
request send a sourcelist request in parallel, to have the latencies of the two
requests overlap.

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

  parent reply	other threads:[~2021-03-31 16:41 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
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 [this message]
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-q6Nj8BO4Kh@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).