[CRIU] dedup and memory tracking

[Pavel Tikhomirov]

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.


Best Regards, Tikhomirov Pavel.


2014-07-06 23:46 GMT+04:00 J F <jgmb45 at gmail.com>:

> On Thu, Jun 12, 2014 at 4:00 PM, Pavel Tikhomirov <snorcht at gmail.com>
> wrote:
>
>> Hi, you can try this script on the folder where your iterative
>> snapshots lay(are created). And send log to us.
>> You need to do it while snapshots creation process(in progress).
>>
>> Best Regards, Tikhomirov Pavel.
>>
>
>
> Hi,
>
> See attached - sorry to respond so late - was away.
>
> Let me know if there is something else you want me to try and/or find a
> way to reproduce with an off the shelf application.
>
> -J
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140710/49e0ce34/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: v2.zip
Type: application/zip
Size: 5250 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140710/49e0ce34/attachment-0001.zip>