No, you can't. The performance will be lower, except very few cases (high cache hit rate after warmup, highly compressible data and use ZFS compression).
As @fabian already told you, the writes don't matter if you use a SSD slog. They are either async and get written to disk on txg commits or...
Oh, I didn't notice the Z3. With ZFS-type RAID you get the speed of the single slowest disk in the pool. It is all about capacity & redundance, not performance.
I cannot find the memory related settings. You say ZFS ARC is limited to 32GB, but ZFS takes more than that (e.g. write buffers).
You say 9 VMs, but no information about they memory allocation. No word for containers either.
The reason I'm interested in this is because I've hit the same issue...
I don't think you need to set anything to have a fair scheduling between tasks. You set when you need one thing to get more CPU time than the others.
For example, you have 3 VMs. First one has 1000, the others have 500. So there is a total of 2000, 50% is going to the first VM, 25% to 2nd VM...
Which brings back the question on why do we need it inside PVE. Are there any PVE specific changes that Promox does to the main repository?
I understand that you guys want to provide "stable" packages but that's the purpose of pvetest repository, as far as I know.
How do you think Proxmox will be able to resize your partitions & filesystem? By magically connecting with a hidden SSH key and apply fdisk and resize2fs?
https://pve.proxmox.com/wiki/Resize_disks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.