Thin vs Thick Provisioning
What Thin and Thick Provisioning Mean
Thin vs thick provisioning describes how much host storage a virtual disk takes up when it is created. A thick disk reserves its full advertised size immediately, while a thin disk uses space only as the guest writes data to it.
A virtual disk is a file, or a set of files, on the host that the virtual machine (VM) sees as a hard drive. The guest operating system reads and writes blocks as if it were using a physical disk, and the hypervisor stores those blocks in an image file. Common formats include qcow2, used with KVM (a Linux hypervisor); VMDK, used by VMware products; and VHDX, used by Microsoft Hyper-V.
The choice matters because host storage is finite. A 100 GB disk created as thick uses 100 GB of free space on day one, even if the guest has written only 5 GB. The same disk created as thin starts small and grows as data is written.
Trade-offs Between Speed, Space and Risk
Thick disks are predictable. Their space is guaranteed, so the guest never finds the host out of room, and writes do not need to allocate new space on the fly. Some thick disks are also zeroed when created, which makes creation slower but keeps later writes steady.
Thin disks use space efficiently. Many VMs have large disks that are mostly empty, so thin provisioning lets a host store more VMs than the sum of their disk sizes. This is a form of overcommitment, the same idea behind overselling CPU and memory. The cost is that storage must be allocated as the guest grows, which adds a little overhead to writes, and free space can run out without warning.
Consider a host with a 1 TB storage volume and 20 VMs, each with a 100 GB thin disk. If the VMs average 15 GB of real data, the volume is fine. If the average grows to 60 GB, the volume fills and VMs can stop or fail to save data. That is the main operational risk of thin provisioning, so good providers monitor free space and set alerts well in advance.
Deleting files inside a guest does not shrink a thin disk on the host by itself. Space is returned only when the guest sends TRIM (or discard) commands, which tell the storage layer which blocks no longer hold data. Snapshots add further layers on top of a disk, as explained in what a VM snapshot is.
Frequently asked questions
Is thin provisioning bad for performance?
Not usually for light workloads. A thin disk adds a small cost when the guest writes to space that has not been allocated yet, because the storage must allocate it first. Thick disks avoid that cost but use their full size from the start. For busy databases, administrators often prefer thick disks to keep latency predictable.
Can a thin virtual disk be converted to thick?
Yes. Most hypervisors and disk tools can convert between the two, but conversion copies data and temporarily needs free space on the host. Check that the storage can hold the full size of the disk before converting a thin disk to thick, and keep a copy of the original file until the converted one has been tested.