[pve-devel] adding a vm workload scheduler feature

Alexandre DERUMIER aderumier at odiso.com
Tue Nov 17 17:59:54 CET 2015


>> I think that any load/cpu metric will be difficult(unstable). 
>> I would simply use static values like cpu count or max. memory. 
>
>or static weight. 

For my personnal usage, I don't think it'll work, because I have a lot of differents workload at different time,
and some vms can use sometime 0% cpu and 80% at spike hours.

But indeed, dynamic stats is not easy to resolve.


Ovirt has a planned feature which use optaplanner

http://www.ovirt.org/Features/Optaplanner
This seem to do some kind of heuristics and maths (out of my competence ;), to known which vm migrate.





Another interesting whitepaper with algorithms
"Dynamic Load Balancing of Virtual Machines using QEMU-KVM"
http://research.ijcaonline.org/volume46/number6/pxc3879263.pdf


----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mardi 17 Novembre 2015 16:51:23
Objet: Re: [pve-devel] adding a vm workload scheduler feature

> On November 17, 2015 at 4:37 PM Dietmar Maurer <dietmar at proxmox.com> wrote: 
> 
> 
> > >>Last but not least, how do you keep the load that migration generates from 
> > >>impacting auto-migration decisions? 
> > 
> > Good question . I think we should use rrds to do average stats of cpu usage. 
> 
> I think that any load/cpu metric will be difficult(unstable). 
> I would simply use static values like cpu count or max. memory. 

or static weight. 


More information about the pve-devel mailing list