You are using NVMEs, so you can safely use JBOD mode.
I think that the size should be for a single disk, but you can experiment on that. If the
LVs are too small, you can just extend them or even recreate them.
What is you network speed ?
If your network bandwidth matches your NVMEs' combined Read speed - then avoid dedup
and compression unless you really need them.
Most probably your NVMEs have a 4096 sector size . If yes, you will need vdo with
'--emulate512'. Yet, tuning VDO for such fast devices is not a trivial task.
Most probably you can configure a VDO per each NVME (or even per pertition/lv) , and
configure it with compression and dedup disabled (emulate512 only if needed).
Also check the UDS index topic, as it is quite important:
https://access.redhat.com/documentation/en_us/red_hat_enterprise_linux/7/...
If your network is slower than your disks, you can enable dedup and compression. Also
gluster has a setting called 'cluster.choose-local' . You can enable it in order
to tell the FUSE driver to prefer local brick instead those over the network.
Best Regards,
Strahil Nikolov
В сряда, 2 декември 2020 г., 14:10:21 Гринуич+2, dofranklin(a)port-orange.org
<dofranklin(a)port-orange.org> написа:
I am about to setup a new hyperconverged setup with the following
3 host setup
2 x nvme 240gb hd for OS on each host (raid)
3 x nvme 7 tb hd for vm storage on each host (no raid card)
500gb RAM per each host
I am confused during the gluster setup portion using the web ui setup wizard. When asked
for the LV size do I input the maximum size of the hard drive on a single host or do I
combine the total capacity of the matching hard drives on all 3 host? Example that I
would be putting in is hard drive: /dev/nvme1p1 capacity 7tb or should it be 21tb
(combined capacity of the matching single HD on the other host). Or is there a better
method you recommend? And since I am using nvme hard drive would you recommend using
dedup and compression or no?
Thanks
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CLIXBOMZ7EE...