SSD drives are not possible on the budget we are on.
We allocate around 80% of the space in the LV partition when we fill up the whole node. as already explained the issues we have had is with SolusVM due to the KVM implementation is not as good. as let's say Proxmox.
The promox VM currently has 10 more virtual machines then the SolusVM test box. during a OS install the %wa will rise around 16.5%wa, while the Proxmox will rise around 2.67%wa. Including it has around 30-50% faster install speeds.
When the SolusVM node is full it can take between 40-50 minutes for a OS reinstall, on the proxmox node around 5 minutes. when the node is empty it will still take around 15 minutes. see the differences?
You're joking, right? 102GB worth of VMs will tear that RAID10 (probably SATA?) apart.
I'm pretty sure it's a typo of 12 GB.
█ Fraud Record - Stop Fraud Clients, Report Abusive Customers.
█ Combine your efforts to fight misbehaving clients. █ HarzemDesign - Highest quality, well designed and carefully coded hosting designs. Not cheap though. █ Large and awesome portfolio, just visit and see!
Then you'll either need to increase the budget, or give up.
The #1 bottleneck is I/O, and no software choice can wiggle out of it.
The bottlecheck is not the I/O, simply the issue is the software due to the amount of virtual machines.
As per example because SolusVM/KVM does not have hugepage support including many other implementations that they need to add currently. The actual issues we face with SolusVM & KVM is CPU issues apart from slow I/O.
While using proxmox we have not had any CPU issues apart from when we allocate high number of CPU's to a guest we then have issues where the VPS will consume high amounts of server load jump from 50 % - 500%.
We do not have any IO issues when using proxmox either.
That same issue happens with SolusVM but a daily occurrence. when a VM reboots.