Bugzilla – Full Text Bug Listing
| Summary: | [performance] Performance regression in CleanUpPerfTest#testCodeStyleCleanUp() | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Satyam Kandula <satyam.kandula> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r |
| Version: | 3.8 | Keywords: | performance |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 374441 | ||
| Bug Blocks: | |||
|
Description
Satyam Kandula
Deepak, please investigate. http://download.eclipse.org/eclipse/downloads/drops/S-3.8M4-201112091447/performance/eplnx2/Scenario415.html CleanUpPerfTest#testSortMembersCleanUp() also shows a similar regression. http://download.eclipse.org/eclipse/downloads/drops/S-3.8M4-201112091447/performance/eplnx2/Scenario421.html http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/performance/eplnx2/Scenario426.html http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/performance/eplnx2/Scenario432.html This were OK till 3.7.1 and I do not see anything that has changed in this area... > This were OK till 3.7.1 and I do not see anything that has changed in this
> area...
The "..." mean, you're investigating deeper now, right?
> The "..." mean, you're investigating deeper now, right?
Yes.
I ran the test with all milestone builds, there looks to be a slowdown in M3 and then a slight improvement in M6 3.7 Elapsed Process: 968ms (95% in [892ms, 1.04s]) Measurable effect: 134ms (1.3 SDs) (required sample size for an effect of 5% of mean: 78) M2 Elapsed Process: 970ms (95% in [896ms, 1.04s]) Measurable effect: 129ms (1.3 SDs) (required sample size for an effect of 5% of mean: 72) M3 Elapsed Process: 1.04s (95% in [927ms, 1.14s]) Measurable effect: 191ms (1.3 SDs) (required sample size for an effect of 5% of mean: 137) M6 Elapsed Process: 996ms (95% in [901ms, 1.09s]) Measurable effect: 166ms (1.3 SDs) (required sample size for an effect of 5% of mean: 112) As I mentioned in comment 3 I do not see anything that changed in JDT UI which would explain this. My best guess at this point are the new static analysis features introduced in this release. More specifically, resource leak warnings were added in M3 (bug 349326), the analysis requires computation of type hierarchies of (almost) all types encountered in code. Also in M3 some of the new code was executed all the time i.e. even when the resource leak options were off, this was improved a little during M6. No action required until bug 374441 is fixed. 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. |