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 E41F51FF165 for ; Thu, 9 Oct 2025 08:37:04 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 01685172FD; Thu, 9 Oct 2025 08:37:10 +0200 (CEST) Message-ID: Date: Thu, 9 Oct 2025 08:36:35 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Thomas Lamprecht , Proxmox Backup Server development discussion References: <20251008134344.3512958-1-d.csapak@proxmox.com> <20251008134344.3512958-8-d.csapak@proxmox.com> <965ca958-d7ec-4d7e-aed0-d97acf22691d@proxmox.com> Content-Language: en-US From: Dominik Csapak In-Reply-To: <965ca958-d7ec-4d7e-aed0-d97acf22691d@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1759991764134 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.028 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: [pbs-devel] [PATCH proxmox-backup v2 6/6] api: admin: datastore: implement streaming content api call X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On 10/8/25 9:49 PM, Thomas Lamprecht wrote: > Am 08.10.25 um 15:43 schrieb Dominik Csapak: >> this is a new api call that utilizes `proxmox_router::Stream` to provide >> a streaming interface to querying the datastore content. >> >> This can be done when a client requests this api call with the >> `application/json-seq` Accept header. >> >> In contrast to the existing api calls, this one >> * returns all types of content items (namespaces, groups, snapshots; can >> be filtered with a parameter) >> * iterates over them recursively (with the range that is given with the >> parameter) >> >> The api call returns the data in the following order: >> * first all visible namespaces >> * then for each ns in order >> * each group >> * each snapshot >> >> This is done so that we can have a good way of building a tree view in >> the ui. > > I guess you did not get around to test some more performance / memory > usage here? Might be nice to have whatever stats you did compare encoded > in the commit message here. no, not yet, but I wanted to do some testing today. I'll send an update when I have more info. > > I.e. that part of you and my text from patch 6/6 from the v1: > > Am 03.10.25 um 13:55 schrieb Thomas Lamprecht: >> Am 03.10.25 um 10:51 schrieb Dominik Csapak: >>> interesting side node, in my rather large setup with ~600 groups and ~1000 >>> snapshosts per group, streaming this is faster than using the current >>> `snapshot` api (by a lot): >>> * `snapshot` api -> ~3 min >>> * `content` api with streaming -> ~2:11 min >>> * `content` api without streaming -> ~3 min >>> >>> It seems that either collecting such a 'large' api response (~200MiB) >>> is expensive. My guesses what happens here are either: >>> * frequent (re)allocation of the resulting vec >>> * or serde's serializing code >> >> You could compare peak (RSS) memory usage of the daemon as side-effect, >> and/or also use bpftrace to log bigger allocations. While I did use bpftrace >> lots of times, I did not try this specifically to rust, but I found a >> shorth'ish article that describes doing just that for rust, and looks like >> it would not be _that_ much work (and could be a nice tool to have in the >> belt in the future): >> >> https://readyset.io/blog/tracing-large-memory-allocations-in-rust-with-bpftrace _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel