[CRIU] dedup and memory tracking

[J F]

On Wed, Jul 9, 2014 at 4:57 PM, Pavel Tikhomirov <snorcht at gmail.com> wrote:

> Please provide output of "./criu show -f <file>" on pagemap-*.img (2-nd
> iteration)
>
> Also I have patch for criu to monitor memory consumption of process, it
> can show
> if your program has high memory consumption rates. But it's not yet
> complete,
> though it works and i can post it here.
>
> Not important: Sorry, i thought the question was about auto-dedup,
> but it's about dirty-tracking, though you can also test auto-dedup.
>
> As I can see in mem_usage_migr.log you do only one snapshot, -- yes?
> Please test on couple of iterative snapshots(~10).
> do snapshots like this:
> start mem_usage_migr.sh
> 1: criu dump --track-mem -R -D $dir/1/
> 2-9: criu dump --auto-dedup --track-mem -R --prev-images-dir=$dir/i-1/
> -D $dir/i/
> 10: criu dump --auto-dedup --track-mem --prev-images-dir=$dir/9 -D $dir/10
> stop mem_usage_migr.sh
>
> Thanks,
> Pavel
>


See attached. I applied your patch to criu v1.3-rc1 and followed your
steps.

Let me know if there is something else I can try.

Best, J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140711/95db82a4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mem_usage.zip
Type: application/zip
Size: 30004 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140711/95db82a4/attachment-0001.zip>