Register now or log in to join your professional community.
This means that creating a 100GB virtual disk actually consumes 100GB of physical disk space, which also means that the physical storage is unavailable for anything else, even if no data has been written to the disk.
Thick provisioning contrasts with thin provisioning, which provisions storage on an as-needed basis. Thin provisioning helps to avoid wasted physical capacity and can save businesses on up-front storage costs. However, thick provisioning has the benefit of lesslatency because all storage is allocated at once when virtual machines are created.
thin provisioning resources assigned are as per the data written is not assigned to VM at once
Thick provisioning space allocated to VM is assigned at once and is consumed from data-store at time of allocation
When you select thick provisioning ,the amount of space allocated is acquired and reserved exclusively for that particular VM whereas in Think provisioning the amount of space is allocated on demand basis until it reaches the limit that you have allocated for that VM.
For Ex: if i choose 10 GB of space for a VM,in thick it reserves full 10GB of space for that particular VM.
In thin provisioning if i chose 10 GB ,it means that i am setting up the limit for that VM,whatever data is being stored on VM ,it will be giving out the space to it on demand basis but the limit of space is 10GB.
In Thick provisioning space allocated to VM is assigned at once and is consumed from datastore at time of allocation while in case of thin provisioning resources assigned are as per the data written on disk of VM. Space is reserved and is allocated on demand and is not assigned to VM at once
