qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: Strategic decision: COW format


From: Anthony Liguori
Subject: Re: [Qemu-devel] Re: Strategic decision: COW format
Date: Wed, 23 Feb 2011 09:50:43 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Lightning/1.0b1 Thunderbird/3.0.10

On 02/23/2011 09:37 AM, Avi Kivity wrote:
On 02/23/2011 05:31 PM, Anthony Liguori wrote:

what about snapshots? Are we okay having a feature in a prominent format that isn't going to meet user's expectations?

Is there any hope that an image with 1000, 1000, or 10000 snapshots is going to have even reasonable performance in qcow2?


Are thousands of snapshots for a single image a reasonable user expectation? What's the use case?


Checkpointing. It was the original use-case that led to qcow2 being invented.

I still don't see.  What would you do with thousands of checkpoints?

For reverse debugging, if you store checkpoints at a rate of save, every 10ms, and then degrade to storing every 100ms after 1 second, etc. you'll have quite a large number of snapshots pretty quickly. The idea of snapshotting with reverse debugging is that instead of undoing every instruction, you can revert to the snapshot before, and then replay the instruction stream until you get to the desired point in time.

For disaster recovery, there are some workloads that you can meaningful revert to a snapshot provided that the snapshot is stored at a rate of something frequency (like once a second). Think of something like a webserver where the only accumulated data is logs. Losing some of the logs is better than losing all of the logs.

Regards,

Anthony Liguori





reply via email to

[Prev in Thread] Current Thread [Next in Thread]