Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I read in one of the VMware KB articles that snapshots will directly affect VM performance.

But my team keeps asking me how snapshots can affect performance.

I would like to give them solid reason behind the statement the snapshots are performance killers.

Can anyone explain a little bit theory about how snapshots are actually affecting the performance? Is it just because Disk I/O rate of hard disk would be slow?

share|improve this question
Not sure if this is the KB article you read or not. I thought I would add it as reference. – Aaron Copley Sep 20 '12 at 14:56
up vote 23 down vote accepted

When you create a snapshot, the original disk image is "frozen" in a consistent state, and all write accesses from then on will go to a new differential image. Even worse, as explained here, the differential image has the form of a change log, that records every change made to a file since the snapshot was taken. This means, that read accesses would have to read not only one file, but also all difference data (the original data plus every change made to the original data). The number increases even more when you cascade snapshots.

share|improve this answer
Best explanation. You are not only doubling IOPS, but there is CPU overhead in calculating the block-level difference. – Aaron Copley Sep 20 '12 at 14:55
After reading this article linked by Aaron Copley (…) it seem worse than that. A Snapshot is not a differential image, it's a change log, so if you write the same data on the same place 10 times, the snapshot will increase it's size by 10 multiplied the size of data you wrote. Instead a differential image should be more efficient because it should overwrite the data rewritten at the same location. – Max Sep 25 '12 at 7:18
@Ansgar Wiechers: Did you read Max comments? He mentioned that as it is maintaining just change log it is worse than having different image. If that concept is more accurate. Please edit your answer. I felt your explanation is good and i would like to make it as answer. – Samselvaprabu Sep 26 '12 at 5:35
@Samselvaprabu Updated. – Ansgar Wiechers Sep 26 '12 at 10:45
@zespri The problem affects all virtualization platforms using this kind of snapshot technology, including Hyper-V. – Ansgar Wiechers Nov 8 '13 at 13:37

When you create a snapshot on a VM this creates a Delta Disk and the operating system writes to this file instead of the original VMDK. This file is called VM_Name-Delta.VMDK but if the system needs to refers to a file before the snapshot it will refers to VM_Name.VMDK increasing the I/O of this operation. If you take multiple snapshots you are referring to the last delta file of the last snapshot not the original VMDK thus increasing I/O.


OS ---> Snapshot (File A Created) ---> (Snapshot File B Created)

If I need to refer to File A it will be looking through 3 VMDK's to find this.

Also if you include the memory state of the VM at the time of snapshotting this creates a this again is a delta file and refers to the original memory files if needed.

A file is created this lists all the files created at the time of the snapshot process

share|improve this answer

As far as I can tell, VMWare is using copy-on-write logic to implement their snapshots. Therefore, when you create one, every operation done on your VM (eg. almost everything in runtime) would cause a little bit of the VM to be copied until the whole thing was essentially cloned.

Another performance issue with this is that reads would have to cascade to the original copy if the working copy doesn't yet have data (because nothing changed to cause a copy).

If you want to have the snapshots as a backup but can't tolerate a small performance decrease, consider cloning the VM instead.

share|improve this answer

As the size and number of snapshots on a virtual machine increase, so does the number of storage command operations within vmkernel. For each storage command issued by the virtual machine guest OS, multiple storage command operations may be necessary to traverse the entire snapshot chain to read the most appropriate block of data.

Copied from a Blog post

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.