<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 4:57 PM, Pavel Tikhomirov <span dir="ltr"><<a href="mailto:snorcht@gmail.com" target="_blank">snorcht@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Please provide output of "./criu show -f <file>" on pagemap-*.img (2-nd iteration)</div>
<div><br></div><div>Also I have patch for criu to monitor memory consumption of process, it can show</div>
<div>if your program has high memory consumption rates. But it's not yet complete,</div><div>though it works and i can post it here.</div><div><br></div>Not important: Sorry, i thought the question was about auto-dedup,<div>
but it's about dirty-tracking, though you can also test auto-dedup.<div>
<br></div><div>As I can see in mem_usage_migr.log you do only one snapshot, -- yes? <div>Please test on couple of iterative snapshots(~10).<div>do snapshots like this: </div><div>start mem_usage_migr.sh</div><div>1: criu dump --track-mem -R -D $dir/1/</div>
<div>2-9: criu dump --auto-dedup --track-mem -R --prev-images-dir=$dir/i-1/ -D $dir/i/</div><div>10: criu dump --auto-dedup --track-mem --prev-images-dir=$dir/9 -D $dir/10</div><div>stop mem_usage_migr.sh</div><div><br></div>
<div>Thanks,</div><div>Pavel</div></div></div></div></div></blockquote><div><br></div><div><br></div><div>See attached. I applied your patch to criu v1.3-rc1 and followed your steps. </div><div><br></div><div>Let me know if there is something else I can try.</div>
<div><br></div><div>Best, J</div><div><br></div><div><br></div><div><br></div><div> </div></div></div></div>