[CRIU] Size of memory used by a program at the moment of checkpointing

[Pavel Emelyanov]

On 01/19/2015 08:31 PM, Thouraya TH wrote:
> Hello Mr Pavel :)
> 
> *Statistics files http://criu.org/Statistics are the same with lxc-checkpoint  ?*
> For example, stats-restore file is empty if i use vim:
> vim stats-restore
> ^F3     W^Q^@^@^@^R^O^Hp^PO^Xͷ^E Ź^G(<8d>^N
> 
> i try also with :  *criu show stats-restore *
> uid: 0
> gid: 0
> euid: 0
> egid: 0
> suid: 0
> sgid: 0
> fsuid: 0
> fsgid: 0
> cap_inh: 0:0
> cap_prm: 0xfdfeffff:0x1c
> cap_eff: 0xfdfeffff:0x1c
> cap_bnd: 0xfdfeffff:0x1c
> secbits: 0

That's not stats-restore, that's creds-$pid.img file.
I wonder how this could happen. Did you toss the files
around while doing C/R?

> .............................
> 
> *i  can't find stats-dump file ! *

What's the command you dump and restore the container with?
If it's lxc-checkount, then I would ask you to trace it to
find out what criu command it launches.

> root at g-2:/home/ImGLXC1Worker# ls
> cgroup.img      creds-189.img  fdinfo-13.img  fs-289.img    ids-989.img      mm-384.img          pagemap-985.img  pipes.img         signalfd.img
> core-1008.img   creds-1.img    fdinfo-14.img  fs-292.img    ids-991.img      mm-985.img          pagemap-987.img  pstree.img        sk-queues.img
> core-172.img    creds-271.img  fdinfo-15.img  fs-376.img    ids-993.img      mm-987.img          pagemap-989.img  reg-files.img     stats-restore
> core-189.img    creds-284.img  fdinfo-16.img  fs-384.img    ifaddr-8.img     mm-989.img          pagemap-991.img  remap-fpath.img   timerfd.img
> core-1.img      creds-289.img  fdinfo-2.img   fs-985.img    inetsk.img       mm-991.img          pagemap-993.img  restore.log       tmpfs-dev-38.tar.gz.img
> core-271.img    creds-292.img  fdinfo-3.img   fs-987.img    inotify.img      mm-993.img          pages-10.img     route-8.img       tmpfs-dev-39.tar.gz.img
> core-275.img    creds-376.img  fdinfo-4.img   fs-989.img    inventory.img    mountpoints-11.img  pages-11.img     sigacts-1008.img  tmpfs-dev-40.tar.gz.img
> core-276.img    creds-384.img  fdinfo-5.img   fs-991.img    ipcns-msg-9.img  netdev-8.img        pages-12.img     sigacts-172.img   tmpfs-dev-41.tar.gz.img
> core-277.img    creds-985.img  fdinfo-6.img   fs-993.img    ipcns-sem-9.img  netlinksk.img       pages-13.img     sigacts-189.img   tmpfs-dev-42.tar.gz.img
> core-284.img    creds-987.img  fdinfo-7.img   ids-1008.img  ipcns-shm-9.img  ns-files.img        pages-14.img     sigacts-1.img     tty.img
> core-289.img    creds-989.img  fdinfo-8.img   ids-172.img   ipcns-var-9.img  packetsk.img        pages-15.img     sigacts-271.img   tty-info.img
> core-292.img    creds-991.img  fdinfo-9.img   ids-189.img   iptables-8.img   pagemap-1008.img    pages-1.img      sigacts-284.img   tunfile.img
> core-376.img    creds-993.img  fifo-data.img  ids-1.img     mm-1008.img      pagemap-172.img     pages-2.img      sigacts-289.img   unixsk.img
> core-384.img    dump.log       fifo.img       ids-271.img   mm-172.img       pagemap-189.img     pages-3.img      sigacts-292.img   utsns-10.img
> core-985.img    eventfd.img    filelocks.img  ids-284.img   mm-189.img       pagemap-1.img       pages-4.img      sigacts-376.img   veth0
> core-987.img    eventpoll.img  fs-1008.img    ids-289.img   mm-1.img         pagemap-271.img     pages-5.img      sigacts-384.img
> core-989.img    ext-files.img  fs-172.img     ids-292.img   mm-271.img       pagemap-284.img     pages-6.img      sigacts-985.img
> core-991.img    fanotify.img   fs-189.img     ids-376.img   mm-284.img       pagemap-289.img     pages-7.img      sigacts-987.img
> core-993.img    fdinfo-10.img  fs-1.img       ids-384.img   mm-289.img       pagemap-292.img     pages-8.img      sigacts-989.img
> creds-1008.img  fdinfo-11.img  fs-271.img     ids-985.img   mm-292.img       pagemap-376.img     pages-9.img      sigacts-991.img
> creds-172.img   fdinfo-12.img  fs-284.img     ids-987.img   mm-376.img       pagemap-384.img     pipes-data.img   sigacts-993.img
> 
> Have you an idea please ?
> Thanks a lot.
> Best Regards.
> 
> 
> 
> 2015-01-15 13:36 GMT+01:00 Thouraya TH <thouraya87 at gmail.com <mailto:thouraya87 at gmail.com>>:
> 
>     Hello Mr Pavel :)
> 
>     Thanks a lot for your answer.
>     OK. I'll see statistics files.
> 
>     Best Regards.
> 
>     2015-01-12 10:51 GMT+01:00 Pavel Emelyanov <xemul at parallels.com <mailto:xemul at parallels.com>>:
> 
>         On 01/02/2015 09:00 PM, Thouraya TH wrote:
>         > Hello,
>         >
>         > Please, I am doing the dumping processof the matrix multiplication program.
>         > My question: do CRIU provides detail about the size of memory used by the
>         > program of matrix multiplicationat the moment of checkpointing ?
> 
>         CRIU generates files with statistics after dump and after restore. The
>         files are stats-dump and stats-restore in the image/work dir and are
>         described here [1].
> 
>         Do you need more than that? If yes, let's discuss :)
> 
>         [1] http://criu.org/Statistics
> 
> 
>