Community
Participate
Working Groups
Task ist still updates itself (thus consuming 10% of build time sometimes) although i have it open in a resource perspective, which i have hidden under my current java perspective
Created attachment 2766 [details] task list
The alternative is to avoid updating the tasks view incrementally when hidden. However, this would require a full refresh when it is shown, which can be very expensive. Usually this tradeoff only makes sense when the cost of a full refresh is low.
Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug.
Presumably, you could turn off refresh if you could tell the table really isn't visible (since it would need to be refreshed completely when it is made visible anyway). Are widgets in hidden perpsectives made invisible? Should they be?
Right now the tasks view does a full refresh anyway after each build. We should be able to turn it off when it's invisible and just record if it's dirty... in fact, we could probably save a good chunk of memory if we clear its entire contents if it's invisible and dirty.
I thought the full refresh was still done incrementally. If you clear it, it will be expensive when shown. But deferring the refresh sounds good. Should suffice to track partVisible changes.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
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. If you have further information on the current state of the bug, please add it. 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.
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.
