Community
Participate
Working Groups
Build Identifier: 1-0-0_2010_08_07-698-gf801931 We had performance issues on a grid table with > 200'000 rows Our findings: getItems() which copies from List to Array is called to many times, even when only the number of items is needed after replacing: - all method calls like item.getParentItem().getItems().length by item.getParentItem().getItemCount() - and all getItems()[index] calls by getItem(index) in Grid.java and GridItem.java we improved performance by 75% Reproducible: Always
Hi all, I checked out and did some tests. Can I work on it?
(In reply to Mirko Paturzo from comment #1) > Hi all, > > I checked out and did some tests. Can I work on it? Sure! Can you take the bug yourself now?
YEAH!
Fixed with: http://git.eclipse.org/c/nebula/org.eclipse.nebula.git/commit/?id=79ae80eaf87cba17dc0e1a742a97fb9c53dbaec9 Gerrit: https://git.eclipse.org/r/#/c/25254/ Mirko please take the honors of closing this bug.
Hi all, using the tool jvisualvm, I verified that the method Grid.items.indexOf was very slow. avoiding this method, there was a significant increase in performance. Happy Easter to all. Mirko