qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 07/16] migration: Create x-multifd-group paramet


From: Juan Quintela
Subject: Re: [Qemu-devel] [PATCH 07/16] migration: Create x-multifd-group parameter
Date: Mon, 13 Mar 2017 17:49:59 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

"Daniel P. Berrange" <address@hidden> wrote:
> On Mon, Mar 13, 2017 at 01:44:25PM +0100, Juan Quintela wrote:
>> Indicates how many pages we are going to send in each bach to a multifd
>> thread.
>
>
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index b7cb26d..33a6267 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -988,6 +988,9 @@
>>  # @x-multifd-threads: Number of threads used to migrate data in parallel
>>  #                     The default value is 2 (since 2.9)
>>  #
>> +# @x-multifd-group: Number of pages sent together to a thread
>> +#                     The default value is 16 (since 2.9)
>> +#
>>  # Since: 2.4
>>  ##
>>  { 'enum': 'MigrationParameter',
>> @@ -995,7 +998,7 @@
>>             'cpu-throttle-initial', 'cpu-throttle-increment',
>>             'tls-creds', 'tls-hostname', 'max-bandwidth',
>>             'downtime-limit', 'x-checkpoint-delay',
>> -           'x-multifd-threads'] }
>> +           'x-multifd-threads', 'x-multifd-group'] }
>>  
>>  ##
>>  # @migrate-set-parameters:
>> @@ -1062,6 +1065,9 @@
>>  # @x-multifd-threads: Number of threads used to migrate data in parallel
>>  #                     The default value is 2 (since 2.9)
>>  #
>> +# @x-multifd-group: Number of pages sent together in a bunch
>> +#                     The default value is 16 (since 2.9)
>> +#
>
> How is this parameter supposed to be used ? Or to put it another way,
> what are the benefits / effects of changing it from its default
> value and can an application usefully decide what value to set ? I'm
> loathe to see us expose another "black magic" parameter where you can't
> easily determine what values to set, without predicting future guest
> workloads

We have multiple threads, we can send to each thread the number of pages
that it needs to send one by one, two by two, n x n.  The bigger the
number, the less locking to do, and then less contention.  But if it is
too big, we could probably end with too few distribution.  Reason to add
this parameter is that if we send page by page, we end spending too much
time in locking.

Later, Juan.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]