public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27982] New: debuginfod client maximum-transfer-size and -time parameters
Date: Mon, 14 Jun 2021 21:16:10 +0000	[thread overview]
Message-ID: <bug-27982-10460@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27982
           Summary: debuginfod client maximum-transfer-size and -time
                    parameters
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

DEBUGINFOD_TIMEOUT is a good way to catch servers that are too slow to *start*
transmitting a file.  But we have no way of limiting total download time or
space.  A user might prefer to have his debugger fetch only quick & small
files, and make do without the bigger ones.  Some transitive dependencies of
e.g. gnome programs are huge: 3GB of LLVM debuginfo, 1GB of webkitgtk, etc.
etc.

We could add a $DEBUGINFOD_MAXSIZE and/or $DEBUGINFOD_MAXTIME parameters to the
client side environment variable suite.  The MAXSIZE one could be communicated
to the server in the query as an extra header, so it can quickly respond with
some HTTP error code (since it can generally find out the destination file
sizes prior to actually decompressing them); it can also be enforced during
download, as soon as a Content-Length: header is received.  The MAXTIME one
could be added as a debuginfod-client.c main loop parameter.

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

             reply	other threads:[~2021-06-14 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 21:16 fche at redhat dot com [this message]
2021-06-15 14:30 ` [Bug debuginfod/27982] " fche at redhat dot com
2021-07-19 15:29 ` nsanci at redhat dot com
2021-09-15 17:34 ` 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-27982-10460@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).