| poor performance in Tree Views [message #16249] |
Thu, 12 April 2007 12:27  |
Eclipse User |
|
|
|
Hi,
I just tried to use a Tree in an TreeView like in the examples of the M2
build.
I added about 1000 Childs to a root node and experienced very poor
performance
on the Client rendering this tree. The Rendering on the client (javascript)
seems to take a very long time.I figured out that the request from client to
server just take 250 ms
but the initial rendering took about 13 seconds on a 2 GHz Client. I looked
into the javascipt which
was generated by RAP and i found huge code for every node entry in the tree
which is 1000 times repeated for every node. Most of the code is for styling
purpose like Fonts, color, etc. this could be optimized for example with a
dynamic
generated style sheet which colud be referenced by every node. Do i have to
addres this issue to the RAP guys or to quooxdoo guys ? Or do you have any
other hint ?
Regards,
Thomas
|
|
|
| Re: poor performance in Tree Views [message #16263 is a reply to message #16249] |
Thu, 12 April 2007 16:36  |
| Eclipse User |
|
|
|
Originally posted by: rsternberg.innoopract.com
Hi Thomas,
Thomas Kühne schrieb:
> I just tried to use a Tree in an TreeView like in the examples of the M2
> build.
> I added about 1000 Childs to a root node and experienced very poor
> performance
> on the Client rendering this tree. The Rendering on the client (javascript)
> seems to take a very long time.I figured out that the request from client to
> server just take 250 ms
> but the initial rendering took about 13 seconds on a 2 GHz Client. I looked
> into the javascipt which
> was generated by RAP and i found huge code for every node entry in the tree
> which is 1000 times repeated for every node. Most of the code is for styling
> purpose like Fonts, color, etc. this could be optimized for example with a
> dynamic
> generated style sheet which colud be referenced by every node. Do i have to
> addres this issue to the RAP guys or to quooxdoo guys ? Or do you have any
> other hint ?
First, JavaScript code is only generated for custom fonts (setting
custom colors is not yet supported by TreeItem). If you use the standard
font, the code generated by RAP for one tree item should look
essentially like this:
var w = new org.eclipse.rap.rwt.widgets.TreeItem( wm.findWidgetById(
"w414" ) ); wm.add( w, "w791", false ); w.setLabel( "Node_92" );
Rendering a tree with 1000 items is very slow even without custom fonts.
Nearly all the time needed for adding tree items is spent somewhere in
the qooxdoo code (custom.js) which is hard to profile as it contains no
line breaks. I'm sure there is potential for optimization, but please
note that we are still in an early state of development and not yet in
the phase of optimization.
However, if you find a way to create a qx.ui.treefullcontrol.Tree with
1000 items notably faster, we're interested to hear about it.
Regards,
Ralf
|
|
|
Powered by
FUDForum. Page generated in 0.06439 seconds
Home