yes, I'm working for something like that.
I have already remove 1 extra call with
if (me.rendered) {
me.applyState(sp.get(stateid));
}
Now I'm looking to compare timeframe
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
Envoy
> comment // me.applyState(sp.get(stateid));
>
> disable the 2 extra calls (But changing timeframe combobox doesn't work
> anymore)
I guess you just need to check if timeframe or rrdcffn really changed - if not
we do not need to reload?
___
pve-de
Applied, thanks. But I tried to simplify the patch - please an you test if it
still works?
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Montag, 10. Juni 2013 09:27
> To: pve-devel@pve.p
> >>And how do you detect 'binary' data?
> I have sent a patch for gif & png, should be enough (Don't know for .jar)
Applied, thanks!
I also disabled compression for jar files (those are simply zip files).
___
pve-devel mailing list
pve-devel@pve.proxmo
>>I'm looking for second extra call.
in panel.RRDView.js
comment // me.applyState(sp.get(stateid));
disable the 2 extra calls (But changing timeframe combobox doesn't work anymore)
I'll try to found to avoir these reloads on panel first init.
- Mail original -
De: "Alexandre DE
> I have notice a small 0,5s lag when selecting a vm in the tree,
>
> when the vm summary tab open, I see the 4 rrds loaded 3 times and
> javascript is blocking (see firebug screenshot in attachment).
>
> This only happen when opening the vm, switching between vms panel tabs
> (summary<->hardware
Hi,
I have notice a small 0,5s lag sometimes when selecting a vm in the tree,
when the vm summary tab open, I see the 4 rrds loaded 3 times and javascript is
blocking.
This only happen when opening the vm, switching between vms panel tabs
(summary<->hardware tab) don't have this problem.
Wiki is not yet updated, but
From gui, you have a new "move disk" button, on your vm hardware tab. (works
offline or online)
command line is : qm move_disk
- Mail original -
De: "Fabrizio Cuseo"
À: "Martin Maurer"
Cc: "proxmoxve (pve-u...@pve.proxmox.com)" ,
pve-devel@pve.pr
>>And how do you detect 'binary' data?
I have sent a patch for gif & png, should be enough
(Don't know for .jar)
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 10 Juin 2013 13:33:30
Objet: RE: [pve-devel] about pveproxy g
Theses formats are already compressed.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Signed-off-by: Alexandre Derumier
---
PVE/HTTPServer.pm |9 ++---
PVE/REST.pm |6 +++---
2 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/PVE/HTTPServer.pm b/PVE/HTTPServer.pm
index 46c217e..6911b10 100755
--- a/PVE/HTTPServer.pm
+++ b/PVE/HTTPServer.pm
@@ -264,14
> >> And also disable it for png generated from rrds ?
> >Oh, I guess that would make sense.
>
> Maybe this could apply for all binary datas ?
> I think only text,html,json should be compressed.
And how do you detect 'binary' data?
___
pve-devel mailing
>>One simple hack would be to simply set the 'running' flag in the resource
>>store
>>when the user press start/stop on the client side.
Yes, I think it could be a great!
I'll try to make a patch.
Thanks!
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-dev
>>AFAIK this just burns CPU power.
You are right, I have done test with a 85k non compressed ressource json:
gzip default : 19k
gzip level9 : 18k
so no benefit
>> And also disable it for png generated from rrds ?
>Oh, I guess that would make sense.
Maybe this could apply for all binary data
> >>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.
> use default compression level
>
> Does it make sense to force it to compression level = 9 ?
AFAIK this just burns CPU power.
> And also disable it for png generated from rrds ?
Oh, I guess that would make sense.
___
pve-devel mailing list
pve-deve
> Worst case is that you can wait 9,999second if the resource is updated just
> before the vm stop/start.
Sure , I did not say it is perfect ;-) But it is acceptable on average (for me).
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.pro
Hi all,
We just uploaded a bunch of packages to our pvetest repository
(http://pve.proxmox.com/wiki/Package_repositories) , including a lot of bug
fixes, code cleanups, qemu 1.4.2 and also a new quite cool new feature -
storage migration ("qm move").
A big Thank-you to our active community for
About pveproxy gzip compression,
I notice that in
HTTPServer.pm
my $comp = Compress::Zlib::memGzip($content);
use default compression level
Does it make sense to force it to compression level = 9 ?
And also disable it for png generated from rrds ?
_
>>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
Signed-off-by: Alexandre Derumier
---
PVE/API2/Qemu.pm | 33 ++---
1 file changed, 18 insertions(+), 15 deletions(-)
diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
index b99045e..5b88ee7 100644
--- a/PVE/API2/Qemu.pm
+++ b/PVE/API2/Qemu.pm
@@ -130,25 +130,28 @@ m
changelog: correctly handle volumes without storeid
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
22 matches
Mail list logo
