| Summary: | [perfs] Regression for StatePerformanceTest#testResolution100() | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Frederic Fusier <frederic_fusier> |
| Component: | Framework | Assignee: | equinox.framework-inbox <equinox.framework-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, tjwatson |
| Version: | 3.6 | Keywords: | test |
| Target Milestone: | 3.6 RC1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 286955 | ||
|
Description
Frederic Fusier
This looks to be caused by the fix in bug269185. We are trading off reduction of memory usage for a small jump in execution time. I also can see a similar regression (ie. which appeared exactly on the same build) on following test: - StatePerformanceTest#testResolution500() My tool didn't notice me for it as it's just at the -10% threshold, sometimes over and sometimes below, hence there are never 3 consecutive builds having this failure... (In reply to comment #1) > This looks to be caused by the fix in bug269185. We are trading off reduction > of memory usage for a small jump in execution time. Hence, the best solution in this case is to add a comment in these tests. I added a regression comment to the four tests you have identified. |