From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4CA951FF183 for ; Wed, 3 Dec 2025 21:47:04 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EC60D134A5; Wed, 3 Dec 2025 21:47:29 +0100 (CET) Message-ID: <5d53eb03-4e75-4a2b-8d08-bbd200db018e@proxmox.com> Date: Wed, 3 Dec 2025 21:47:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox Datacenter Manager development discussion , Dominik Csapak References: <20251203143439.3595966-1-d.csapak@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20251203143439.3595966-1-d.csapak@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1764794800337 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.021 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pdm-devel] [PATCH datacenter-manager 1/2] server: api: subscription: improve cache and update behavior X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" Am 03.12.25 um 15:34 schrieb Dominik Csapak: > To avoid long load times in the ui, use only cached entries for > subscription info in the GET subscription api call by default, but add a > 'force-load' parameter to restore the previous behavior. > > The check_subscription api call now always load from all remotes to get > the most up-to-date information from them. hmm, this gets a bit confusing to me. Renaming the param to "cache-only" would make that a bit better, as your name suggests that we always load now, but with that param passed we still use the cache as long as the age there is below max-age. That said, I'm not sure this is the route I'd like to go at all, so just lets not rush it and revisit this in a few days/weeks again. What I'd probably would prefer is caching the unknown result and early returning when that is recent enough. Actually, it might be nice to have a global unknown (or offline) remote (+ nodes?) cache, where we save when a remote was unknown and if it was often in a certain time period we skip it from querying at all and short circuit that to unknown in all places. This naturally needs to be fleshed out and needs a bit of care, e.g., users should be able to see (and manually clear) this state. _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel