[pve-devel] tasks / ressources

[Alexandre DERUMIER]

>>The VM GUI directly pools the VM status each second, so you gain not much here 
>>( well, the resource store gets newer values). 

It's true if you are on the vm when stop/start.

Now try to right-click->start another vm, you need to wait because you don't pool the vm status directly.

Worst case is that you can wait 9,999second if the resource is updated just before the vm stop/start.




----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Lundi 10 Juin 2013 08:33:23 
Objet: RE: [pve-devel] tasks / ressources 

> > What I would like to have, is: 
> > 
> > - vm status : pooling each second (pvestatd / pve-manager) 

The VM GUI directly pools the VM status each second, so you gain not much here 
( well, the resource store gets newer values). 

> > - vm,storage,node stats : pooling each X (10?) seconds (pvestatd/ pve- 
> > manager) 
> 
> This would multiply cluster traffic by factor 10?! 

For me it is still unclear what problem you want to solve? The current GUI (RessourceTree) updates 
the resource store within 5.5 seconds on average. This is not particularly fast, but is known 
to work up to > 1000 VMs. Also, the VM GUI directly queries the VM status each second. 

.