User Tools

Site Tools


computing:proxmox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
computing:proxmox [2024/01/07 00:04] oemb1905computing:proxmox [2024/01/07 00:09] (current) oemb1905
Line 173: Line 173:
 If ram is an issue, make sure to throttle arc. In my case, I let zfs run free and tightly provision the VMs. Each rig and use case will be different; adjust accordingly. Above, I already shared the command to determine your physical CPUs / sockets. Here's how to determine all three: If ram is an issue, make sure to throttle arc. In my case, I let zfs run free and tightly provision the VMs. Each rig and use case will be different; adjust accordingly. Above, I already shared the command to determine your physical CPUs / sockets. Here's how to determine all three:
  
-  lscpu | grep "CPU(s): "+  lscpu | grep "thread"
   lscpu | grep "per socket"   lscpu | grep "per socket"
   lscpu | grep "Socket(s)"   lscpu | grep "Socket(s)"
-  CPU(s): 48+  Thread(s) per core2
   Core(s) per socket: 12   Core(s) per socket: 12
   Socket(s): 2   Socket(s): 2
  
-This is for an 8-core i7 Dell XPS 8900. ThusI have 8*4*32 cores to play with. As for RAM, I have 64GB total, so subtracting 4Gb for the OS, I have 32GB left for the VMs with roughly 32GB being allocated for zfs. PVE is very strict in interpreting allocated RAM and will OOM kill VMs if it senses it is short. This is in contrast, for example, with virsh which will allow sysadmins to run how they see fit even at risk of virsh crashing. For this reason, either expand your rig, adjust arc, or tightly provision your VMs, or all three. I personally just tightly provisioned my VMs as I want zfs to use as much RAM as it needs. If you prefer to throttle arc, here's how:+To determine vCPUs, you do threads*cores*physical-socketsor (12*2)*(12)*(2) 576 for a Supermicro with 2x Xeon e5-2650 v4 chips. As for RAM, I have 64GB total, so subtracting 4Gb for the OS, I have 32GB left for the VMs with roughly 32GB being allocated for zfs. PVE is very strict in interpreting allocated RAM and will OOM kill VMs if it senses it is short. This is in contrast, for example, with virsh which will allow sysadmins to run how they see fit even at risk of virsh crashing. For this reason, either expand your rig, adjust arc, or tightly provision your VMs, or all three. I personally just tightly provisioned my VMs as I want zfs to use as much RAM as it needs. If you prefer to throttle arc, here's how:
  
   sudo nano /etc/modprobe.d/zfs.conf   sudo nano /etc/modprobe.d/zfs.conf
computing/proxmox.txt · Last modified: 2024/01/07 00:09 by oemb1905