Community
Participate
Working Groups
not sure, but that sounds a bit slow for 2000 markers (the default size in the filter) that'd be 7 seconds just to update the task list.
not really major - but a heads up (although i suspect thet you know)
Actually, for 2000 items when you're filtering, the time to display should be somehwere around "0". After all, all you see is: There are too many items to display. To see the items in this window, adjust the filter settings. (I know, that makes the filter useless.) More timings (by the watch) of how long Eclipse is "Updating" after a complete build: (Win2k, PIII-866, 1 Gig of ram -- the only filter I'm using limits #of items displayed) 827 items (no filter): ~123 seconds Setting the filter to 10 and rebuilding: ~50 seconds Removing the filter (without rebuilding): ~5 seconds 2000 items (of ~7500): Killed after 15 minutes (during which the UI was *completely* unresponsive, not even repainting.) So, what *is* Eclipse doing when it's Updating after a complete build but before it displays items? Whatever it is, it's pretty intensive....
*** Bug 45168 has been marked as a duplicate of this bug. ***
Heh. This one was a satisfying one to fix. :-) *** This bug has been marked as a duplicate of 44443 ***
