From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Eneko Lacunza <elacunza@binovo.es>
Subject: [PVE-User] Advice request for new cluster
Date: Thu, 27 Mar 2025 10:22:27 +0100 [thread overview]
Message-ID: <mailman.257.1743067357.359.pve-user@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6689 bytes --]
From: Eneko Lacunza <elacunza@binovo.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Advice request for new cluster
Date: Thu, 27 Mar 2025 10:22:27 +0100
Message-ID: <1adce0d3-b1cb-4cf3-85da-4f37c6a31ca1@binovo.es>
Hi all,
We're in the process of designing and procuring a new PVE HCI cluster.
We will service about 6,000 tenants, each running two docker containers,
one with PostgreSQL and the other a python web application.
Containers will be hosted in VMs, 250 tenants per VM. VMs will have
512GB RAM and 16-32 vcores. 4 VMs per server.
Based on current data, we expect to be memory constrained; CPU,
networking and disk (Ceph) not being our main concern.
We're looking to optimize our cost per GB of RAM, so our current plan is
to deploy 6 servers with 2,3TB RAM and 2 EPYC CPU sockets, each with 48
cores, 4x25 Gbps network and 3x7,68T disks for Ceph. The more expensive
alternative would be to deploy 12x 1,15TB RAM 1 EPYC servers (+30%
adquisition and about +40% running costs)
I have been reading reports about NUMA performance issues on Proxmox
mailing lists and elsewhere. Memory bandwith issues for example.
Based on what I understood, and seeing that we'll have more than 2,000
not very demanding containers in each server, I think those NUMA issues
shouldn't be a problem in our use case.
I'll be very grateful on any suggestion or comment about this NUMA issue
and our cluster design.
Cheers
Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project
Tel. +34 943 569 206 | https://www.binovo.es
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
reply other threads:[~2025-03-27 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.257.1743067357.359.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=elacunza@binovo.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal