From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A7E76385559F; Fri, 17 Mar 2023 16:16:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A7E76385559F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1679069762; bh=LKXDoIdmx08kQOlg0xvOa8X9YCM17OPcFMUJ2yWBXWs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rc/sqkW2Gumbj4dERoSa6QTzQiElaRVg3mbCnFdJUl+JnjwTiPSDzPlIWj20V4oQB p8HO35wgVYx28xhQE0gHWAtNfO0c+TboaUL4c1cIUWwsu/SxrlaR2cn3vbNbtiIcvv ygtVHVpCV24YBsWhI/RYtekfBSPqioospSlTMDzc= From: "amerey at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/30221] Negative cache should differentiate failure types Date: Fri, 17 Mar 2023 16:16:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amerey at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30221 Aaron Merey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amerey at redhat dot com --- Comment #9 from Aaron Merey --- (In reply to Vicki Pfau from comment #7) > I did, and in comment 2 I already explained why I think it's a bad idea.(= In > reply to Frank Ch. Eigler from comment #6) > > (In reply to Vicki Pfau from comment #2) > > > 404 and the like *may* be transient, but the fact of the matter is th= at > > > *most* of the time it won't be And it's a cache, not a definitive ans= wer > > > saying this will never exist. Having a 404 cache for 10x the amount o= f time > > > as a Ctrl-C > >=20 > > I don't understand - a ctrl-C should not result in a cached artifact at= all. > > If that's happening, we should fix that. >=20 > Okay, that is kinda weird then. I'm seeing it in gdb--perhaps it's a gdb > issue then. The issue was in libdebuginfod itself. I merged a fix for this: https://sourceware.org/pipermail/elfutils-devel/2023q1/006050.html > > > I'm already dealing with gdb taking well > > > over 30 seconds to start running a program with a bunch of shared obj= ect > > > dependencies that aren't in debuginfod... > >=20 > > Uncached misses from debuginfod tend to take on the order of millisecon= ds, > > much less than seconds. Do you have a trace of what's happening? > > (DEBUGINFOD_VERBOSE=3D1 or something like that?) >=20 > The issue appears to be the debuginfod server taking a not-insignificant > amount of time per request (500ms - 2s I'd estimate) to report the absence > of an associated artifact. Perhaps this is just an issue with how the ser= ver > is configured. I'm using the elfutils server, but I've seen the same issue > on Arch's server (the distro I'm using). It's worth noting too that some > users will undoubtedly have higher latency. A way to asynchronously initi= ate > requests so you can have multiple going at once would be great to try and > alleviate this somewhat, but it doesn't look like there's a way to do this > yet. There has been some discussion about gdb downloading from debuginfod in background worker threads. I would like to get this feature added eventual= ly. --=20 You are receiving this mail because: You are on the CC list for the bug.=