From: Milian Wolff <mail@milianw.de>
To: elfutils-devel@sourceware.org
Subject: parallel downloads of multiple debuginfo files
Date: Fri, 08 Apr 2022 22:53:14 +0200 [thread overview]
Message-ID: <6158828.BCo7LnDCpQ@milian-workstation> (raw)
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Hey all,
one more debuginfod question: Would it be possible to extend the API to allow
downloading of multiple debug info files in parallel?
The `debuginfod_find_*` API currently only supports looking at multiple server
urls in parallel. I would like to ask multiple files in parallel.
The use case would be profiling tools like the ones I'm working on
(perfparser, heaptrack, ...). There, you usually have a list of libraries that
you know you'll hit sooner or later. Thus it would be more efficient to start
downloading all debug information files in parallel directly. At least
compared to the current status quo with dwfl where we would iteratively find
individual debug information files, each time blocking the process.
Parallel downloads from a single server would definitely increase the load
there though, when done naively. Have you thought about adding support for
something like HTTP/3's ability to download mutiple assets over a single
connection (maybe even in parallel)?
Thanks
--
Milian Wolff
mail@milianw.de
http://milianw.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-04-08 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:53 Milian Wolff [this message]
2022-04-08 20:54 ` Frank Ch. Eigler
2022-04-08 20:58 ` Milian Wolff
2022-04-08 21:31 ` Frank Ch. Eigler
2022-04-15 13:11 ` Mark Wielaard
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=6158828.BCo7LnDCpQ@milian-workstation \
--to=mail@milianw.de \
--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).