Customers deploying DataMiner in a virtual environment have the option to provision all disk space from the beginning (thick provisioning) or let the disk expand as needed (thin provisioning). The difference between these two methods is explained in Virtual Disk Thin Provisioning (vmware.com).
Looking at DataMiner Compute Requirements | DataMiner Docs, we would like to know if we can use thin provisioning or if it is discouraged.
Please address each application separately: DataMiner, Cassandra, and OpenSearch.
Thanks
Hi Miguel,
That doesn't make any difference for DataMiner. You can choose the provisioning you want; this is more related to how you want to manage your VMs and your storage. Thin provisioning is more efficient for your storage but be careful with overprovisioning.
Some might claim thick provisioning has better performance, but these days that would be hardly noticeable. DataMiner does most things in-memory anyhow, so for DataMiner it's definitely no problem to go for thin provisioning.
For the databases you could potentially argue about it, but the differences will be so small that you won't notice it while using DataMiner. So, also for the databases you can go for thin provisioning if you want. But note that STaaS is still the preferred option for storage of course ;-).
In other words, you can choose thin or thick provisioning for DataMiner, Cassandra and OpenSearch, and choose what fits your operations best.
Bert