Community
Participate
Working Groups
Looking at I20090127-0100 results, it looks like several "Separate JRE Build" tests got a regression on all performance machines. Here are the detailed numbers: Win XP Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM) builds Separate S. JRE Build; S. JRE Build; JRE Build -debug links M4 I20081211-1908 0.3% -0.1% 0.4% I20081216-0800 -0.1% -0.1% 0.4% I20090106-0800 -0.1% -0.2% 0.3% I20090113-0918 -0.5% -0.7% 1.1% I20090120-0920 -16.5% -19.8% -12.2% N20090122-2000 -17.3% -20.0% -14.9% I20090125-2000 -18.1% -21.6% -16.0% I20090127-0100 -17.7% -21.3% -16.1% SLED 10 Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM) builds Separate S. JRE Build; JRE Build -debug M4 I20081211-1908 1.9% 1.2% I20081216-0800 2.6% -1.5% I20090106-0800 0.0% 2.0% I20090113-0918 2.9% 0.0% I20090114-1322 0.8% 0.7% I20090120-0920 -6.8% -3.3% N20090122-2000 -7.1% -4.4% I20090125-2000 -7.7% -5.0% I20090127-0100 -8.6% -5.5% It clearly looks like a regression was introduced since build I20090120-0920
What is the status for this issue? Is there a chance that something will be done for M7?
No one is actively working on this. However, someone on the debug team will try to look at this during M7.
Needs investigation.
Removed from summary since we have not had a chance to investigate. Leaving open.
(In reply to comment #4) > Removed from summary since we have not had a chance to investigate. Leaving > open. > Hence remove the dependency to 3.5 performances root bug...
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.