[pve-devel] tasks / ressources

[Dietmar Maurer]

> >>You have up to 16 different cluster nodes, and they update at different
> times.
> >>
> >>But I simply never had problems polling each second.
> Ok for a big cluster, now if you have a only a single node, it doesn't make
> sense.

Maximal time to get new values is 11seconds. This time will increase if you update less often.

> in pvestatd,
> 
> my $updatetime = 10;
> 
> so update status occur each 10seconds.
> 
> 
> 
> >>pvestatd is a separate processs - so what do you miss?
> As a storage status can be "slow", do
> update_qemu_status(),update_storage_status(),update_node_status() in
> parallel.
> This can speedup things.

It does not matter if that is slow - why?

> > (My main problem is that I can see noticable delays when start/stop vms)
> >>I doubt this is related to pvestatd?
> 
> But this is pvestatd which pool QemuServer::vmstatus() to see if the vms are
> stop/started, right ?
> So pooling each 10s, you can have delay on status refresh in gui.

yes.

> 
> 
> 
> What I would like to have, is:
> 
> - vm status : pooling each second (pvestatd / pve-manager)
> - vm,storage,node stats : pooling each X (10?) seconds (pvestatd/ pve-
> manager)

This would multiply cluster traffic by factor 10?!