From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BB5CE3858CDA; Sat, 11 Mar 2023 01:32:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB5CE3858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678498354; bh=iGe1PAsuvgW2JveLldMvLdQr64VtTE4ZIaT67hFhDUs=; h=From:To:Subject:Date:From; b=EnVOMK2fxK7E+4kwskhvXAuz0kZJ2qj3WrSekbmWcAEHobDMXHXqb71V5qntHCXFS VYHUq+lZoPFWWqkzyXmS9DhzU2EX8fF+xHwlYR96C6HqXpnuWfDi+CdaDXXJ+nqux7 z6KXdqE/2SyMA5hp8HqItKH5fqRxnMi2chht1Qro= From: "vi at endrift dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/30221] New: Negative cache should differentiate failure types Date: Sat, 11 Mar 2023 01:32:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: vi at endrift 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: 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 Bug ID: 30221 Summary: Negative cache should differentiate failure types Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: debuginfod Assignee: unassigned at sourceware dot org Reporter: vi at endrift dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- Having a negative cache is essential for performant lookups with debuginfod, but it doesn't differentiate between different types of failure, e.g. trans= ient (timeout, interrupted, etc) and non-transient (server responded 404 or 410)= . A 404 error is unlikely to be resolved in as short a timespan as a transient error, and some servers don't have great debug info coverage, not to mention local builds. It's very annoying to have to hit tons of builds only to get a 404 so frequently, so it'd be a good idea to have different cache timeouts = for different failure types. I looked into how the negative cache works, and it looks like it's just the presence of a 0 byte file. Unfortunately, this means there's no metadata associated at all, and I'm not sure how tacking on metadata should work in = the first place. xattrs perhaps? --=20 You are receiving this mail because: You are on the CC list for the bug.=