The weaknesses of vsphere and VMware snapshots

When a snapshot is created, the virtual machine performs a read operation, and Hypervisor examines the snapshot vmdk to see if there are any chunks that have been read.
If so, the block is provided for the virtual machine from the snapshot, and if not, the virtual machine needs to read the underlying VMDK. If there is only one snapshot, this is not a problem, but a repetition to read the VMDK.
However, if a large number of snapshots exist, such as one per day within two weeks, then hypervisor needs to look up the chunk in 14 snapshot files, which consumes a lot of read I/O.

The weaknesses of vsphere and VMware snapshots