>>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.
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. > (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. 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) ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Alexandre DERUMIER" <aderum...@odiso.com>, "Stefan Priebe - Profihost AG" <s.pri...@profihost.ag> Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 10 Juin 2013 06:40:15 Objet: RE: [pve-devel] tasks / ressources > Also, I don't known for you, but my pvestatd daemon refresh values each 10 > seconds. > So why pve-manager is pooling each second ? You have up to 16 different cluster nodes, and they update at different times. But I simply never had problems polling each second. > > I have around 50vms on this host, > Polling vm status is fast, but the storage status take around 2s (could be > great > have a seperate worker/thread/something parallel for this) But after that > it's > waiting 7s. pvestatd is a separate processs - so what do you miss? > (My main problem is that I can see noticable delays when start/stop vms) I doubt this is related to pvestatd? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
