2x Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHzwhat are the host cpu ?
I ran the command but have no idea what I'm looking at:Can you maybe also check the pressure stats? They can often give a hint of potential bottlenecks:
Code:head /proc/pressure/*
This is another host ?! in first post, you speak about two ProLiant G9 & Shared Storage on a TrueNAS.2x Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
ProLiant DL380p Gen8
I Mis-spoke in the first post - thought they were gen 9's they are both gen 8's.This is another host ?! in first post, you speak about two ProLiant G9 & Shared Storage on a TrueNAS.
anycase, these old cpus need mitigations disabled as @davemcl says
FWIW, I've switched from HyperV to PVE on two HP ProLiant ML350 G8 , one with E5-2620 ( RDS VM + SQL VM ) the other with E5-2620v2, users didn't notice differences. and with now a PBS alongside PVE , I'm confident if host die to restore on fresh HW.
The only thing that was meant for the local storage was just the pve install. Does the hypervisor install drive impact the operation of the guests?in addition of disabling mitigations, I think storage is the bottleneck, because 2 hdd as local drive even with FBWC can't be responsive running Wn10 guests. Test with a Datacenter SSD locally attached, more over outside the HP SmartArray, if on embedded SATA controller , don't forget to re-enable Disk Write Cache in BIOS.
Shared Storage need to be tested too , with another current gen HW host.
I'm not ZFS user, but ZFS R1 is slow , write speed is same as a single drive + I'm not sure about what is "Cache VDEV on a 120GB SSD",
Yes when host need to SWAP on it when it does not have enough RAMThe only thing that was meant for the local storage was just the pve install. Does the hypervisor install drive impact the operation of the guests?
I think you can get this 5 minutes Win10 boot delay with a bad ZFS configuration , like RAID Z1 on HDD (I'm not sure cache can do magic here , this is another ZFS topic optimization ...)On the ZFS ... 10x 3TB spinning 7200 RPM SAS drives ... but I didn't think it would impact it THAT much to where it takes 5 minutes to log in on a Windows 10 guest.