Community
Participate
Working Groups
I did a sync on my workspace of ~80 projects and enabled change sets with 200 incoming changes. The cache appeared to be taking up 10 MB. The cache is held by a soft reference but we should try to reduce the size since I suspect that most of the entries in the cache are unneeded.
The 10MB may be a bit exaggerated as my profiler seems to over-report on cyclic object graphs when calculating retained size.
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.
Unfortunately there is no time to do this in 3.1
Do you have a better estimate of how much space is being taken up? Does this number scale linearly in the number of projects? Are there simpler, internal representation changes that could reduce the size of the cache, but which did not require a lot of effort to implement?
We fixed a leak in 3.2. However, we coudl save more space by sharing strings.
We do not plan on addressing this issue in 3.3.
Bug 194396 made some improvements in this area. We should profile it again and see how much was saved.
Mass update - removing 3.4 target. This was one of the bugs marked for investigation (and potential fixing) in 3.4 but we ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
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.
