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 C5C799B00 for ; Fri, 18 Nov 2022 12:16:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AF27437995 for ; Fri, 18 Nov 2022 12:16:21 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS for ; Fri, 18 Nov 2022 12:16:21 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id E93F644C30; Fri, 18 Nov 2022 12:16:20 +0100 (CET) Message-ID: <81f3d33d-7a9d-a13f-d0a7-f135cab930d8@proxmox.com> Date: Fri, 18 Nov 2022 12:16:20 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Thunderbird/108.0 Content-Language: en-GB To: Proxmox VE user list , Anton Shevtsov References: <85f2f4f7-df13-adee-3779-358dc05aae92@basealt.ru> From: Thomas Lamprecht In-Reply-To: <85f2f4f7-df13-adee-3779-358dc05aae92@basealt.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: =?UTF-8?Q?0=0A=09?=AWL -0.030 Adjusted score from AWL reputation of From: =?UTF-8?Q?address=0A=09?=BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict =?UTF-8?Q?Alignment=0A=09?=NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF =?UTF-8?Q?Record=0A=09?=SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Max limits questions 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, 18 Nov 2022 11:16:21 -0000 Hi, Am 16/11/2022 um 07:30 schrieb Anton Shevtsov: > Where i can find information about below questions > > VM > > 1. Max vCPU count per VM ? Proxmox VE places no limit on that, so basically how many the PVE host CPU has. With more the KVM acceleration cannot work any more, so it gets rather slow and unpracticable. > > Node host > > 1. How many maximum CPU cores are supported per node? Kernel dependent. For the current supported Proxmox VE 7.2's 5.15 kernel it's 8192 per CPU as you can find out by checking the kernel compile config: grep NR_CPUS /boot/config-5.15.*-pve Multi-Socket systems normally stop at 4 sockets, but we know a setup with 8 sockets that uses Proxmox VE. So I guess 8 * 8192 = 65536 > > 2. Max RAM are supported per node? (i think - unlimited, but..) No not unlimited, Linux currently supports 48- and 57-bit virtual addresses. So, depending on your CPU/Mainboard/... it's something between 2^48 = 256 TiB and 2^57 = 128 PiB. In practice the limit will be currently in the range of 6 TiB for modern (last gen) of Server CPUs. For example, with DDR5 you can get 512 GiB per DIMM and Epyc Genoa CPUs support 12 channels, so 12 * 512 GiB = 6 TiB. cheers, Thomas