This is a multi-part message in MIME format. --------------090604020401030504010604 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Seems to be quite good! Le 22/04/2016 00:14, Greg Sheremeta a =E9crit :
Hi everyone,
If you've experienced this issue and you're able to upgrade to 3.6.5,=20 I'd love to get your feedback on the responsiveness of the webadmin UI=20 now.
Best wishes, Greg
On Sun, Apr 3, 2016 at 11:13 AM, Greg Sheremeta <gshereme@redhat.com=20 <mailto:gshereme@redhat.com>> wrote:
We have patches in review that should fix this in 3.6.5. The underlying problem is a couple of JavaScript memory leaks.
Best wishes, Greg
On Fri, Jan 8, 2016 at 10:41 AM, Nir Soffer <nsoffer@redhat.com <mailto:nsoffer@redhat.com>> wrote:
On Fri, Jan 8, 2016 at 4:42 PM, Alexander Wels <awels@redhat.com <mailto:awels@redhat.com>> wrote: > On Friday, January 08, 2016 04:29:47 PM Nir Soffer wrote: >> On Fri, Jan 8, 2016 at 1:13 PM, Nathana=EBl Blanchet <blanchet@abes.fr <mailto:blanchet@abes.fr>> wrote: >> > Hi all, >> > >> > Since I upgraded engine to 3.6, I noticed that the webadmin takes a lot of >> > ressources whatever is the browser. It can become very slow even for small >> > actions, like changing tabs or editing a vm. The browser activity becomes >> > intensive (100% of cpu) and the processor very hot with a increased fan >> > activity. I suppose javascript to be responsible of this behaviour. Is >> > there a way to reduce the resource allocated to the webadm= in? >> > (This is not a weakness of my laptop which is an i7 cpu with 16GB of RAM) >> >> Sounds like https://bugzilla.redhat.com/1264809 >> >> It was closed because we could not reproduce it with current versions. >> >> I would try first to upgrade to latest 3.6 version, and if you can reproduce >> it, please reopen this bug. >> >> Alexander: can you advice on how to debug this? >> >> Nir > > If you are willing to spend some time helping us debug that would be great as > obviously we are unable to reproduce. If you have Chrome, can you open the > development tools (ctrl-shift-i) and go to the 'Profiles' tab. That should give > you the option to 'Collect Javascript CPU Profile' among other things. Make > sure you select that, and click start. Then go in the web admin and do > something that makes your CPU spike. Let it go for a little bit doesn't have > to be long. > > Go back to the CPU profiles tab and click stop. That will generate a profile and > that profile will include the percentage of CPU usage per method. It should be > sorted by percentage. If you can take a screen shot of that and give me the > exact rpm version, I can use that to de-obfuscate the method name and > hopefully get some useful information.
You can also save such profile to file, and attach it to the bu= g.
When I reorted this, this was also reproducible in Firefox, and both profiles are attached to the bug.
Nir _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
--=20 Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme@redhat.com <mailto:gshereme@redhat.com> 919-741-4016 <tel:919-741-4016>
--=20 Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme@redhat.com <mailto:gshereme@redhat.com> 919-741-4016
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--=20 Nathana=EBl Blanchet Supervision r=E9seau P=F4le Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=E9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr --------------090604020401030504010604 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable <html> <head> <meta content=3D"text/html; charset=3Dwindows-1252" http-equiv=3D"Content-Type"> </head> <body bgcolor=3D"#FFFFFF" text=3D"#000000"> Seems to be quite good!<br> <br> <div class=3D"moz-cite-prefix">Le 22/04/2016 00:14, Greg Sheremeta a =E9crit=A0:<br> </div> <blockquote cite=3D"mid:CAEReEe8h_FXWMjBFExkdLvBT6LVEVtrR2E7CqMA1ouYhH58Y8Q@mail.gmai= l.com" type=3D"cite"> <div dir=3D"ltr">Hi everyone, <div><br> </div> <div>If you've experienced this issue and you're able to upgrade to 3.6.5, I'd love to get your feedback on the responsiveness of the webadmin UI now.</div> <div><br> </div> <div>Best wishes,</div> <div>Greg</div> <div><br> </div> </div> <div class=3D"gmail_extra"><br> <div class=3D"gmail_quote">On Sun, Apr 3, 2016 at 11:13 AM, Greg Sheremeta <span dir=3D"ltr"><<a moz-do-not-send=3D"true" href=3D"mailto:gshereme@redhat.com" target=3D"_blank">gsher= eme@redhat.com</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir=3D"ltr">We have patches in review that should fix this in 3.6.5. The underlying problem is a couple of JavaScript memory leaks. <div><br> </div> <div>Best wishes,</div> <div>Greg</div> <div><br> </div> </div> <div class=3D"gmail_extra"> <div> <div class=3D"h5"><br> <div class=3D"gmail_quote">On Fri, Jan 8, 2016 at 10:41 AM, Nir Soffer <span dir=3D"ltr"><<a moz-do-not-send=3D"true" href=3D"mailto:nsoffer@redhat.com" target=3D"_bla= nk"><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:nsoffer@redhat.c= om">nsoffer@redhat.com</a></a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0= 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div> <div>On Fri, Jan 8, 2016 at 4:42 PM, Alexander Wels <<a moz-do-not-send=3D"true" href=3D"mailto:awels@redhat.com" target=3D"_blank">awels@redhat.com</a>> wrote:<br> > On Friday, January 08, 2016 04:29:47 PM Nir Soffer wrote:<br> >> On Fri, Jan 8, 2016 at 1:13 PM, Nathana=EBl Blanchet <<a moz-do-not-send=3D"true" href=3D"mailto:blanchet@abes.fr" target=3D"_blank"><a class=3D"moz-txt-link-ab= breviated" href=3D"mailto:blanchet@abes.fr">blanchet@abes.fr</a></a>> wrote:<br> >> > Hi all,<br> >> ><br> >> > Since I upgraded engine to 3.6, I noticed that the webadmin takes a lot of<br> >> > ressources whatever is the browser. It can become very slow even for small<br> >> > actions, like changing tabs or editing a vm. The browser activity becomes<br> >> > intensive (100% of cpu) and the processor very hot with a increased fan<br> >> > activity. I suppose javascript to be responsible of this behaviour. Is<br> >> > there a way to reduce the resource allocated to the webadmin?<br> >> > (This is not a weakness of my laptop which is an i7 cpu with 16GB of RAM)<br> >><br> >> Sounds like <a moz-do-not-send=3D"true" href=3D"https://bugzilla.redhat.com/1264809" rel=3D"noreferrer" target=3D"_blank"><a class= =3D"moz-txt-link-freetext" href=3D"https://bugzilla.redhat.com/1264809">h= ttps://bugzilla.redhat.com/1264809</a></a><br> >><br> >> It was closed because we could not reproduce it with current versions.<br> >><br> >> I would try first to upgrade to latest 3.6 version, and if you can reproduce<br=
>> it, please reopen this bug.<br> >><br> >> Alexander: can you advice on how to debug this?<br> >><br> >> Nir<br> ><br> > If you are willing to spend some time helping us debug that would be great as<br> > obviously we are unable to reproduce. If you have Chrome, can you open the<br> > development tools (ctrl-shift-i) and go to the 'Profiles' tab. That should give<br> > you the option to 'Collect Javascript CPU Profile' among other things. Make<br> > sure you select that, and click start. Then go in the web admin and do<br> > something that makes your CPU spike. Let it go for a little bit doesn't have<br> > to be long.<br> ><br> > Go back to the CPU profiles tab and click stop. That will generate a profile and<br> > that profile will include the percentage of CPU usage per method. It should be<br> > sorted by percentage. If you can take a screen shot of that and give me the<br> > exact rpm version, I can use that to de-obfuscate the method name and<br> > hopefully get some useful information.<br> <br> </div> </div> You can also save such profile to file, and attach it to the bug.<br> <br> When I reorted this, this was also reproducible in Firefox, and both profiles<br> are attached to the bug.<br> <span><font color=3D"#888888"><br> Nir<br> </font></span> <div> <div>____________________________________________= ___<br> Users mailing list<br> <a moz-do-not-send=3D"true" href=3D"mailto:Users@ovirt.org" target=3D"_blank">Users@ovirt.org</a><br> <a moz-do-not-send=3D"true" href=3D"http://lists.ovirt.org/mailman/listin= fo/users" rel=3D"noreferrer" target=3D"_blank">http://l= ists.ovirt.org/mailman/listinfo/users</a><br> </div> </div> </blockquote> </div> <br> <br clear=3D"all"> <div><br> </div> </div> </div> <span class=3D"HOEnZb"><font color=3D"#888888">-- <br> <div>Greg Sheremeta, MBA<br> Red Hat, Inc.<br> Sr. Software Engineer<br> <a moz-do-not-send=3D"true" href=3D"mailto:gshereme@redhat.com" target=3D"_blan= k">gshereme@redhat.com</a><br> <a moz-do-not-send=3D"true" href=3D"tel:919-741-4016" value=3D"+19197414016" target=3D"_blank">919-741-40= 16</a><br> </div> </font></span></div> </blockquote> </div> <br> <br clear=3D"all"> <div><br> </div> -- <br> <div class=3D"gmail_signature">Greg Sheremeta, MBA<br> Red Hat, Inc.<br> Sr. Software Engineer<br> <a moz-do-not-send=3D"true" href=3D"mailto:gshereme@redhat.com" target=3D"_blank">gshereme@redhat.com</a><br> 919-741-4016<br> </div> </div> <br> <fieldset class=3D"mimeAttachmentHeader"></fieldset> <br> <pre wrap=3D"">_______________________________________________ Users mailing list <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org">Use= rs@ovirt.org</a> <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman= /listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <pre class=3D"moz-signature" cols=3D"72">--=20 Nathana=EBl Blanchet Supervision r=E9seau P=F4le Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=E9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:blanchet@abes.fr">bl= anchet@abes.fr</a> </pre> </body> </html> --------------090604020401030504010604--