[CRIU] [PATCH 0/7] GSoC 19: Optimizing the Pre-dump Algorithm

[abhishek dubey]

Hi Dmitry,

On 28/08/19 9:43 PM, Dmitry Safonov wrote:
> Late to the party :)
>
> On 8/25/19 2:58 AM, Abhishek Dubey wrote:
>> Performance:
>> ------------
>> $ ./test/zdtm.py run --pre 5 -t zdtm/static/maps04 -f h
>>
>> Splice mode -
>> pre-dump: 0.59
>> pre-dump: 0.06
>> pre-dump: 0.07
>> pre-dump: 0.06
>> pre-dump: 0.06
>> dump: 0.12
>>
>> $ ./test/zdtm.py run --pre 5 -t zdtm/static/maps04 --pre-dump-mode=read -f h
>>
>> Read mode -
>> pre-dump: 0.66
>> pre-dump: 0.06
>> pre-dump: 0.06
>> pre-dump: 0.06
>> pre-dump: 0.06
>> dump: 0.12
>>
>> Average drop : ~ 7%
>> Maximum drop : ~ 13%
> I presume, those are.. seconds?
Yes, its in seconds. using python's time.time()
>
>> Freeze time:
>> ------------
>> $ ./test/zdtm.py run --pre 5 -t zdtm/static/maps04 --show-stats -f h
>>
>> Splice mode -
>> pre-dump: 122235
>> pre-dump: 77514
>> pre-dump: 77912
>> pre-dump: 74940
>> pre-dump: 71977
>> dump: 131208
>>
>> $ ./test/zdtm.py run --pre 5 -t zdtm/static/maps04 --pre-dump-mode=read --show-stats -f h
>>
>> Read mode -
>> pre-dump: 82365
>> pre-dump: 67521
>> pre-dump: 68385
>> pre-dump: 68706
>> pre-dump: 67144
>> dump: 160998
>>
>> Average reduction : ~18%
>> Maximum reduction : ~35%
> Sounds like milliseconds but probably still worth to note that directly.

These values of "frozen time" are grabbed from --show-stats while 
running test-case.

I think these values are usec.

>
> Nice work!
>
> Thanks,
>            Dmitry
-Abhishek