Bugzilla – Full Text Bug Listing
| Summary: | rwt.widgets.Grid.js#isItemSelected slow when many items selected | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Clemens Schneider <hula.bula> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | ASSIGNED --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | tbuschto | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Using a hashmap might be faster, but that would have to be proven before we think ab out how to implement that. The client-side class has been renamed a while ago, but the function under discussion is still there. Change the title accordingly. |
Created attachment 204846 [details] chrome profile of shift-selecting 50000 items in table When having many elements (e.g. 50000) in a table and then doing a shift-select from first to last element, the UI freezes for quite some time. Profiling in chrome shows that most of the time is spent in org.eclipse.rwt.widgets.Tree#isItemSelected (see attachment). Couldn't the check be performed more efficiently?