* [Bug debuginfod/27701] New: use long lived debuginfod-client objects & curl handles
@ 2021-04-06 17:41 fche at redhat dot com
2021-05-01 18:03 ` [Bug debuginfod/27701] " fche at redhat dot com
2021-05-13 1:27 ` fche at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: fche at redhat dot com @ 2021-04-06 17:41 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27701
Bug ID: 27701
Summary: use long lived debuginfod-client objects & curl
handles
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: ---
Discussion of bug #27673 brought light to an important source of inefficiency
in the debuginfod protocol for applications that make repeated queries. The
basic problem is that each time we nuke and recreate a curl handle, any cached
information such as an active keep-alive http connection, or crypto session
keys, are thrown away. Each new connection can take time & CPU, bleeding
latency.
If we retain the curl-easy handles across debuginfod-client calls, rather than
creating/destroying them during Every Call, then much of that setup work is
eliminated, and anti-DoS web firewall concerns also eased. Some estimates here
indicate savings of hundreds of milliseconds per call are available, and even
more if DoS penalties are applied.
debuginfod would itself be a good client to use this tactic to maintain
persistent connections to its federation partners.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug debuginfod/27701] use long lived debuginfod-client objects & curl handles
2021-04-06 17:41 [Bug debuginfod/27701] New: use long lived debuginfod-client objects & curl handles fche at redhat dot com
@ 2021-05-01 18:03 ` fche at redhat dot com
2021-05-13 1:27 ` fche at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2021-05-01 18:03 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27701
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
commit 6c8b68b0245c8754997b4c4b0ff4ba24974e3fdd
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Fri Apr 23 13:04:26 2021 -0400
PR27701: debuginfod client: encourage reused debuginfod_client objects
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug debuginfod/27701] use long lived debuginfod-client objects & curl handles
2021-04-06 17:41 [Bug debuginfod/27701] New: use long lived debuginfod-client objects & curl handles fche at redhat dot com
2021-05-01 18:03 ` [Bug debuginfod/27701] " fche at redhat dot com
@ 2021-05-13 1:27 ` fche at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2021-05-13 1:27 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27701
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=27859
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-05-13 1:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-06 17:41 [Bug debuginfod/27701] New: use long lived debuginfod-client objects & curl handles fche at redhat dot com
2021-05-01 18:03 ` [Bug debuginfod/27701] " fche at redhat dot com
2021-05-13 1:27 ` fche at redhat dot com
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).