Community
Participate
Working Groups
We are using lazyLoading content provider with JFace TreeViewer. when the the no of nodes in the tree is more than > 10000. even the scroll is also taking more time and hanging. i have observed that the viewer.replace itself is taking more than (10s). public void updateElement(Object parent, int index) { long startTime=System.currentTimeMillis(); viewer.replace(parent, index, element); System.out.println("Node time viewer.replace"+index +" : "+ (System.currentTimeMillis()-startTime)); } could any one suggest me how to improve the performance of the same.
Please try with 4.13 version.
(In reply to Andrey Loskutov from comment #1) > Please try with 4.13 version. is this issue fixed in 4.13 version? is there any bug mentioned this issue, Please share me the BUG id.
(In reply to siva ganesh from comment #2) > (In reply to Andrey Loskutov from comment #1) > > Please try with 4.13 version. > > is this issue fixed in 4.13 version? To verify that, please try with 4.13 or even 4.14 M1, because there will be no patch for 4.9 anymore.
(In reply to Andrey Loskutov from comment #3) > (In reply to siva ganesh from comment #2) > > (In reply to Andrey Loskutov from comment #1) > > > Please try with 4.13 version. > > > > is this issue fixed in 4.13 version? > > To verify that, please try with 4.13 or even 4.14 M1, because there will be > no patch for 4.9 anymore. Tried in 4.13 & 4.14M also taking same time. Performance not improved.
(In reply to siva ganesh from comment #4) > Tried in 4.13 & 4.14M also taking same time. Performance not improved. Thanks for verifying that. Can you attach some example project showing performance issue?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
(In reply to siva ganesh from comment #0) > We are using lazyLoading content provider with JFace TreeViewer. > when the the no of nodes in the tree is more than > 10000. even the scroll > is also taking more time and hanging. It looks like a memory/GC issue. The lazy viewer is kind of a misused beast. When you set the size (to 10000+) then the viewer is creating that many stub items. One reason, I guess, is to get the scrollbar dimensions correct. Then on lazy read, the stub items are replaced for real items. One strategy is that you should not set that many items because the user will never page through that list all the way through 10000+ items. Instead, you can try to never show more items than are visible to the user. If that is too complex, just set your maximum to 5k items and provide filtering/selecting to give the user what they want to see. Also, in the nebula project there are alternative faster viewer implementations like Nattable and Grid. > i have observed that the viewer.replace itself is taking more than (10s). Did you use setUseHashLookup(true)?
