[pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations > 0
Alexandre DERUMIER
aderumier at odiso.com
Sun Dec 30 09:39:14 CET 2012
>>What about every 15seconds if no progress has happened? How would
>>you define progress?
Maybe we can check if remaining memory goes up and down.
(So it could also works with qemu 1.4 as we dont have expected_downtime value)
(if remaining memory > last remaing memory){
counter++
}
if(counter == 15){
set_migrate_downtime = migratedowntime + 0.X sec
counter = 0;
}
----- Mail original -----
De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>
À: "Dietmar Maurer" <dietmar at proxmox.com>
Cc: "Alexandre Derumier" <aderumier at odiso.com>, pve-devel at pve.proxmox.com
Envoyé: Dimanche 30 Décembre 2012 09:33:09
Objet: Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations > 0
What about every 15seconds if no progress has happened? How would
you define progress?
I would then start at 0.15s downtime as
default or at custom conf value if defined. If no progress happens I would double the value.
Stefan
Am 30.12.2012 um 06:55 schrieb Dietmar Maurer <dietmar at proxmox.com>:
>> i really like that idea instead of having a fixed downtime of 1s. What is about
>> starting at 0.5s and then add 0.5s every 15 runs?
>
> Yes, we can do that, but may "Every 15 runs if we make no progress"?
>
More information about the pve-devel
mailing list