From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 176028478 for ; Wed, 30 Aug 2023 19:08:08 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EFA2737AD0 for ; Wed, 30 Aug 2023 19:07:37 +0200 (CEST) Received: from mail-oo1-xc33.google.com (mail-oo1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 30 Aug 2023 19:07:36 +0200 (CEST) Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-57361de8878so9718eaf.0 for ; Wed, 30 Aug 2023 10:07:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wolfspyre-com.20230601.gappssmtp.com; s=20230601; t=1693415249; x=1694020049; darn=lists.proxmox.com; h=date:to:in-reply-to:references:message-id:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=9sM5xPXogpoa6Gdclyguv+liCI+aC6MtaweaAvDGxr0=; b=oB+90hPkV9rKpoU1GabD5GEqYfMfLRnkKxjtuDyPut9sFulludcD4B6xGYwGazIg2u pAlKXIc0GQOurEXNwbSOGCv6qTEixE+Db50+XfuxjQH9bVzMpjfk7P84ku88zPocBFFu 3UzgkTMadK28JvYU1/mnKLj1Fo4DnjeBzF7lPPOSsNJ7za9AzbuqyFhiWHl0lWUI4WF0 jahrbP9IPIYwfAfdLGolzNRIRH6gLzBlLqDR3niiegQaSXVPcEwpQh/Mzh52sO4RkXnN 4efFDNgY/kcXf0Auc1qHlKdjhXPTT6XIDljVpXgXCzZk6TMYwZQ4dThquix3iHZWROJr kfbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693415249; x=1694020049; h=date:to:in-reply-to:references:message-id:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9sM5xPXogpoa6Gdclyguv+liCI+aC6MtaweaAvDGxr0=; b=UDuN95ujNbpRccBbhXliCuMSdbMSkyHyhwQkyQ8gd13te9vBKRTETA0Mc/wSfi0XmT jTRWu5HweWfywZhZJdRh7kUeA80g5jkQ3DpLBjm4vnMs94NAr/+9mICXtoE+D0KtqwLm tiqVL/PVuQA9EFCFwbDnxK3Bk0x33DNib77L9lw+qITB+TlS02LM79I6PoU4xaVuUaKi xfpI3wyj1ZnXHpoUdwn8cTyLtZ39hEMmkDzU6gX/iGjLT6J2oDU8o0oljyj8DOS5b3++ K6VHJciQ2aWsLItWYpvaIjyWGo34EpEjKB25ZlrfnJKrQw8AirsEQEgsUtd0EAavm7cu uJLA== X-Gm-Message-State: AOJu0YyhTCKijXi5vxr5yGA/CyCIibwW8vi4xMOQ39j0398LT7eBTIuk dYEuegAxRy8cLX7j89cXxBRM8A== X-Google-Smtp-Source: AGHT+IE+FMws3FcKVvlWNEDVZDJP7aZvSrXJ31VabdpHBZG3t13vr2Yn3lA78jpwRpxXtwb7C+BV2A== X-Received: by 2002:a4a:919c:0:b0:56e:4921:deb0 with SMTP id d28-20020a4a919c000000b0056e4921deb0mr2565973ooh.8.1693415248553; Wed, 30 Aug 2023 10:07:28 -0700 (PDT) Received: from smtpclient.apple (who.wolfspaw.com. [108.221.46.19]) by smtp.gmail.com with ESMTPSA id q1-20020a4aac41000000b0056c91e89f6dsm5983769oon.37.2023.08.30.10.07.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Aug 2023 10:07:28 -0700 (PDT) From: Wolf Noble Mime-Version: 1.0 (1.0) Message-Id: <3F71FA56-CC06-4B2A-9278-B1A19D1496CE@wolfspyre.com> References: In-Reply-To: To: Proxmox VE development discussion Date: Wed, 30 Aug 2023 12:07:17 -0500 X-Mailer: iPhone Mail (21A5319a) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DMARC_MISSING 0.1 Missing DMARC policy HTML_MESSAGE 0.001 HTML included in message MIME_QP_LONG_LINE 0.001 Quoted-printable line longer than 76 chars RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [pve-devel] [RFC storage/proxmox{, -perl-rs} 0/7] cache storage plugin status for pvestatd/API status update calls X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2023 17:08:08 -0000 depends, i suppose, on ( juice > squeeze ) evaluation=E2=80=A6 but I could see ultimately adding flags to the cli / attributes to the api t= o request fresh/tolerate stale / tolerate stale if howStale < time=E2=80=A6 a= llowing for choice=E2=80=A6=20 one could also imagine implementing mechanism to assert that a cached piece o= f information is now definitively no longer accurate=E2=80=A6 however that= =E2=80=99d never catch all the ways the cached data becomes bad data=20 but how deep that rabbit hole goes=E2=80=A6 is=E2=80=A6 well=E2=80=A6=20 i bet there=E2=80=99s likely a few yaks to shave somewhere in the rabbit den= too=E2=80=A6 hasn=E2=80=99t it been said frequently that there are two really hard proble= ms in programming? naming things , caching, and off-by-one errors? [=3D The contents of this message have been written, read, processed, erased= , sorted, sniffed, compressed, rewritten, misspelled, overcompensated, lost,= found, and most importantly delivered entirely with recycled electrons =3D]= > On Aug 22, 2023, at 04:17, Fiona Ebner wrote: >=20 > If operations affecting the values like allocation, resize, etc. would > invalidate the cache, I think we could go for a bit more. But if they > don't, the limit can't be too high IMHO. Otherwise, users will wonder > why the usage on the storage doesn't change after their action. >=20 > And would it make sense to have the cache be opt-in? So that only > pvestatd would use it, but standalone API/CLI calls always get current > values? If there is invalidation like mentioned above, that might not be > needed, but otherwise, I'm a bit afraid that handing out (slightly) > outdated values might trip up some automated scripts doing batch work or > something