public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	Anton Shevtsov <shevtsovay@basealt.ru>
Subject: Re: [PVE-User] Max limits questions
Date: Fri, 18 Nov 2022 12:16:20 +0100	[thread overview]
Message-ID: <81f3d33d-7a9d-a13f-d0a7-f135cab930d8@proxmox.com> (raw)
In-Reply-To: <85f2f4f7-df13-adee-3779-358dc05aae92@basealt.ru>

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




  reply	other threads:[~2022-11-18 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  6:30 Anton Shevtsov
2022-11-18 11:16 ` Thomas Lamprecht [this message]
2022-11-18 11:30   ` Anton Shevtsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81f3d33d-7a9d-a13f-d0a7-f135cab930d8@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-user@lists.proxmox.com \
    --cc=shevtsovay@basealt.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal