Hi,
With Chrome 18 there is a significant slowdown in the qooxdoo layout engine. I
am currently investigating this issue together with some Google engineers. So
far it seems that there are two conditions that triggers that problem.
1. There are content changes for text labels.
2. There is at least one hardware accelerated elements (canvas) on the
page.
With this the browser engine switch to hardware mode and the layout process
become more expensive. Google is checking how they can improve the situation
but although noticed that the current way how qooxdoo handle the layout is not
optimal. Using a single DIV setting innerHTML and the get the size directly
after this would trigger re-parse and re-layout over and over again. They
recommend to batch multiple size requests together. This way only one
re-parse/re-layout is necessary. They believe that this would although improve
performances if there is no hardware accelerated element on the page. A further
improvement would be setting the innerHTML in one JavaScript element and
getting the sizes back in another one. This give the browser engine at least
the chance to do the re-parse/re-layout on another thread while the JavaScript
engine can execute other code that are not depend on the sizes of this elements.
I know that this would be larger changes on the layout pipeline and I hope that
Google can fix this issue on their side. But I wanted to let you know in the
case that other people here on the list run in similar problems after the
Chrome 18 release.
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
