[CRIU] Technical question

[Pavel Emelyanov]

On 02/28/2017 07:17 PM, Rami Addad wrote:
> Rami Addad a partagé des fichiers OneDrive avec vous. Pour les afficher, cliquez sur les liens ci-dessous.
> 
> <https://1drv.ms/t/s%21AnSrSEU9SGBag3sDckQPgvLm93bi>
> 	
> statistic.txt <https://1drv.ms/t/s%21AnSrSEU9SGBag3sDckQPgvLm93bi>
> 	
> 
> <https://1drv.ms/u/s%21AnSrSEU9SGBag3x2OlbNwymfKbOk>
> 	
> dump.sh <https://1drv.ms/u/s%21AnSrSEU9SGBag3x2OlbNwymfKbOk>
> 	
> 
> Dear all,
> 
> 
> for the option  --track-mem we put it in every pre-dump and also in the last dump 
> 
>  and you could observe in the statistic.txt file that there are skipped page and also 
> 
> the freezing time is small and all the others time are small only the frozen time is big 
> 
> 
> 
> and there is the part of script in file dump.sh 
> 
> 
> 
> we think that we have took all the possibility but we always have this big time of dump 

OK, here are the stats for final dump

"dump": {
                "freezing_time": 8017, 
                "frozen_time": 4243423, 
                "memdump_time": 21419, 
                "memwrite_time": 5866, 
                "pages_scanned": 258539, 
                "pages_skipped_parent": 9985, 
                "pages_written": 1356, 
                "irmap_resolve": 0
            }

frozen time is 4 seconds, memdump time is 0.02 seconds, so the time
is spent somewhere else.

First -- try to reduce the verbosity of this final dump, don't use the -vvvvvv
option, leave it to be -v0.
Second, can you show your dump.log file with increased verbosity, there are
timestamps in it, they will help to understand where the time is spent.

-- Pavel