[Top][All Lists]

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

Re: [PATCH] migration/throttle: Add throttle-trig-thres migration parame

From: Eric Blake
Subject: Re: [PATCH] migration/throttle: Add throttle-trig-thres migration parameter
Date: Fri, 21 Feb 2020 08:14:38 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

On 2/20/20 8:57 PM, Keqian Zhu wrote:
Currently, if the bytes_dirty_period is more than the 50% of
bytes_xfer_period, we start or increase throttling.

If we make this percentage higher, then we can tolerate higher
dirty rate during migration, which means less impact on guest.
The side effect of higher percentage is longer migration time.

We can configure this parameter to switch between migration time
firt or guest performance first. The default value is 50.

Signed-off-by: Keqian Zhu <address@hidden>
Cc: Juan Quintela <address@hidden>
Cc: "Dr. David Alan Gilbert" <address@hidden>
Cc: Eric Blake <address@hidden>
Cc: Markus Armbruster <address@hidden>

+++ b/qapi/migration.json
@@ -524,6 +524,10 @@
  #                      compression, so set the decompress-threads to the 
number about 1/4
  #                      of compress-threads is adequate.
+# @throttle-trig-thres: The ratio of bytes_dirty_period and bytes_xfer_period 
+#                       trigger throttling. It is expressed as percentage. The
+#                       default value is 50. (Since 5.0)

Abbreviating feels odd; can you please spell this out as throttle-trigger-threshold?

Can the threshold exceed 100%?

Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

reply via email to

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