Am 10.10.2013 05:33, schrieb Dietmar Maurer: >> I get values between 500ms and 5s depending on connection. One of the biggest >> problems seems to be the tasks and ressources list. Both of them have gzip >> compressed 25kb and pve requests them very often. >> >> Wouldn't it be possible to have something like: >> - get cluster version >> - if cluster version > oldcluster version: >> get ressources >> else >> *do nothing* >> >> Just requesting a version number would be very fast even on slow connections >> and ExtJS does not need to rerender "old" data. > > The problem is that relatively static resource configuration data is mixed > with very dynamic > resource status (cpu usage, memory usage). And we call 'get resources' to > update the GUI > with actual status information. The GUI does not make much sense without that > data.
Oh OK i thought for stuff like that we use the /current requests - but you're right that's only valid for the guests and not for the overall stats. >> Maybe something like this is for the task list also possible like sending the >> newest known task and the server checks whether there are newer ones >> available. > > I think we need a solution based on web sockets. The client can make a web > socket connection > to the API server, and the server simply push status changes to those sockets. That would be very perfect - but out of my knowledge ;-( Stefan _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
