Difference between revisions of "Hypervisor 1RU 2024"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
[[File:Innodisk SATADOM-SL 3TE7 Datasheet BICS5.pdf|page=1|200px|Innodisk SATADOM-SL Datasheet]] | [[File:Innodisk SATADOM-SL 3TE7 Datasheet BICS5.pdf|page=1|200px|Innodisk SATADOM-SL Datasheet]] | ||
| + | |||
| + | https://medium.com/@reefland/over-provisioning-ssd-for-increased-performance-and-write-endurance-142feb015b4e | ||
Revision as of 22:13, 18 August 2024
This is the build about the hypervisor in 2024.
This is a 1 RU server with fast local SSD, aprox 18TB of storage.
Disk Layout
Boot disk = 128g mirror ZFS
ZFS storage
5 vdev's mirrored of the SAS disks 2 mirror NVME 256g partition, but dedicated on the whole disk. This can grow. optional log and l2arc on the boot NVME's
NVME name spaces
The NVME come setup as 1.88T disks:
tnvmcap : 1,880,375,648,256 unvmcap : 375,648,256
I suspect this is a 2.0 TiB (2,199,023,255,552b) provisioned down in the controller or about 85%. moving this to a 1.56TB disk will under provision this and make it perform better in the event we use it as log or write intensive.
Reference material
