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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id D57066A6E7 for ; Fri, 17 Sep 2021 11:36:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C275A2DE1E for ; Fri, 17 Sep 2021 11:36:07 +0200 (CEST) Received: from mail.ud08.udmedia.de (ud08.udmedia.de [194.117.254.48]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id CF6FB2DE0C for ; Fri, 17 Sep 2021 11:36:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=aeppelbroe.de; h=from:to :subject:message-id:date:content-type:mime-version :content-transfer-encoding; s=k1; bh=IfHBrjFhESHrOMEOZeFGDeuXvQN WsgOVaW519Ob/brA=; b=AYi1G8vRYTj7UJCNygISQ70XmqkLHNYFdjo0WuVM/+M CfVZtats657D5bgInWfbehpD2kB3UivdofvOT1RrFoz2BWqk52gxXFRq24+0HCiC HseYbjlqRjdMgSyAj8GkKg+pPXEG5hM0KjOpiZ2Z5gkajyW456AcpTCr4wHuOT68 = Received: (qmail 1799897 invoked from network); 17 Sep 2021 11:29:22 +0200 Received: by mail.ud08.udmedia.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 17 Sep 2021 11:29:22 +0200 X-UD-Smtp-Session: ud08?166p2@MO4EkS3MA9hf3hT8 Received: from localhost (localhost [127.0.0.1]) by baikonur.fritz.box (Postfix) with ESMTP id 0C2B8D27858 for ; Fri, 17 Sep 2021 11:29:22 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at baikonur.orbit.local Received: from baikonur.fritz.box ([127.0.0.1]) by localhost (baikonur.fritz.box [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfXPgZhUSgVp for ; Fri, 17 Sep 2021 11:29:21 +0200 (CEST) Received: from baikonur (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by baikonur.fritz.box (Postfix) with ESMTPS id B3C9BD27857 for ; Fri, 17 Sep 2021 11:29:21 +0200 (CEST) User-Agent: EGroupware API 17.1.007 From: Gregor Burck X-Priority: 3 X-Mailer: EGroupware-Mail To: pve-user Message-ID: <20210917112921.EGroupware.VUEdiWgpWw30Fp0tioEjJWr@heim.aeppelbroe.de> Date: Fri, 17 Sep 2021 11:29:21 +0200 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 1 AWL 0.256 Adjusted score from AWL reputation of From: address BAYES_05 -0.5 Bayes spam probability is 1 to 5% DKIM_INVALID 0.1 DKIM or DK signature exists, but is not valid DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid FORGED_SPF_HELO 1 - HTML_MESSAGE 0.001 HTML included in message KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KHOP_HELO_FCRDNS 0.399 Relay HELO differs from its IP's reverse DNS SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_NONE 0.001 SPF: sender does not publish an SPF Record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [aeppelbroe.de] Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Description: Textversion der Nachricht X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] proxmox-restore - performance issues X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2021 09:36:37 -0000 Hi, I've setup an pve/pbs on the same machine: HP DL380 Gen9 E5-2640 v3 @ 2.60GHz (2 x 8 core) 256 GB RAM 2x 1TB SAMSUNG NVME PM983 12x 8 TB HP SAS HDDs I create with HDDs and NVME an zfs Raid10. I still got restore rates of 50 MB/s on one restore job. If I start multiple jobs parallel the single rate is still on this rate, but I see with iotop that the summary rate is even higher (max around 200 MB/s. When I use htop for the CPU utilisation it seems that an single Job run only on one core, even when there are multiple tasks. So I searching the bottle neck, it realy seems not the HDDs. Any idea so long? Thank for every,.. Bye Gregor