[pve-devel] tasks / ressources
Alexandre DERUMIER
aderumier at odiso.com
Mon Jun 10 06:31:28 CEST 2013
Also, I don't known for you, but my pvestatd daemon refresh values each 10 seconds.
So why pve-manager is pooling 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.
(My main problem is that I can see noticable delays when start/stop vms)
Jun 10 06:23:40 kvm1 pvestatd[227124]: begin node status
Jun 10 06:23:40 kvm1 pvestatd[227124]: end node status
Jun 10 06:23:40 kvm1 pvestatd[227124]: begin update qemu status
Jun 10 06:23:40 kvm1 pvestatd[227124]: end update qemu status
Jun 10 06:23:40 kvm1 pvestatd[227124]: begin openvz status
Jun 10 06:23:40 kvm1 pvestatd[227124]: end openvz status
Jun 10 06:23:40 kvm1 pvestatd[227124]: begin update storage status
Jun 10 06:23:42 kvm1 pvestatd[227124]: end storage status update
Jun 10 06:23:42 kvm1 pvestatd[227124]: begin stale openvz consoles
Jun 10 06:23:42 kvm1 pvestatd[227124]: end stale openvz consoles
Jun 10 06:23:50 kvm1 pvestatd[227124]: begin node status
Jun 10 06:23:50 kvm1 pvestatd[227124]: end node status
Jun 10 06:23:50 kvm1 pvestatd[227124]: begin update qemu status
Jun 10 06:23:50 kvm1 pvestatd[227124]: end update qemu status
Jun 10 06:23:50 kvm1 pvestatd[227124]: begin openvz status
Jun 10 06:23:50 kvm1 pvestatd[227124]: end openvz status
Jun 10 06:23:50 kvm1 pvestatd[227124]: begin update storage status
Jun 10 06:23:51 kvm1 pvestatd[227124]: end storage status update
Jun 10 06:23:51 kvm1 pvestatd[227124]: begin stale openvz consoles
Jun 10 06:23:51 kvm1 pvestatd[227124]: end stale openvz consoles
Jun 10 06:24:00 kvm1 pvestatd[227124]: begin node status
Jun 10 06:24:00 kvm1 pvestatd[227124]: end node status
Jun 10 06:24:00 kvm1 pvestatd[227124]: begin update qemu status
Jun 10 06:24:00 kvm1 pvestatd[227124]: end update qemu status
Jun 10 06:24:00 kvm1 pvestatd[227124]: begin openvz status
Jun 10 06:24:00 kvm1 pvestatd[227124]: end openvz status
Jun 10 06:24:00 kvm1 pvestatd[227124]: begin update storage status
Jun 10 06:24:02 kvm1 pvestatd[227124]: end storage status update
Jun 10 06:24:02 kvm1 pvestatd[227124]: begin stale openvz consoles
Jun 10 06:24:02 kvm1 pvestatd[227124]: end stale openvz consoles
----- 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é: Samedi 8 Juin 2013 17:42:24
Objet: Re: [pve-devel] tasks / ressources
Am 08.06.2013 um 07:29 schrieb Dietmar Maurer <dietmar at proxmox.com>:
>>>> But configurable/stored at the client side?
>> Don't known. Maybe in a cookie client client ?
>
> We can use html local storage for that.
>
>> Or setting this value in a new the user account field ?
>
> The same use connect sometime over fast local network, later using slow VPN.
>
> Maybe we can auto-detect network speed? would that help
Not really but latency / load time of the current / tasks is checkable. So if it takes 1s it doesn't make sense to query it every s.
>
>>
>> ----- Mail original -----
>>
>> De: "Dietmar Maurer" <dietmar at proxmox.com>
>> À: "Alexandre DERUMIER" <aderumier at odiso.com>
>> Cc: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>, pve-
>> devel at pve.proxmox.com
>> Envoyé: Vendredi 7 Juin 2013 14:41:32
>> Objet: RE: [pve-devel] tasks / ressources
>>
>>> Maybe a tunnable value for auto-refresh time could be great ?
>>> (I personaly don't need perf stats (cpu,disk,ram,..) refresh each
>>> second, and it seem to take time (browser cpu) with a lot of vms.
>>
>> Yes. But configurable/stored at the client side?
>
More information about the pve-devel
mailing list