On Mon, Jan 19, 2015 at 07:28:53PM +0900, Hitoshi Mitake wrote: > dog vdi snapshot <vdi> --no-share has a bottleneck: the dog > process. This patch adds a new option --fast-deep-copy to dog vdi > snapshot, which avoid the bottleneck.
It seems to me --no-share and --fast-deep-copy has some relations, they all try to achieve the same purpose, right? But the wording quit differs, which might cause troulbe for uesrs to understand. > If the option is passed to the dog command, actual copying of data > objects are done by sheep processes. So the dog process isn't a > bottleneck in this case. If sheep is busy, e.g, busy with VMs or in recovery state, will this option worsen the situation? That is, make the slow VM slower and in return, this command will be excueted slower and slower. Thanks Yuan -- sheepdog mailing list sheepdog@lists.wpkg.org https://lists.wpkg.org/mailman/listinfo/sheepdog