Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346225 - Small regression in org.eclipse.core.tests.runtime.perf.StartupTest#testApplicationStartup()
Summary: Small regression in org.eclipse.core.tests.runtime.perf.StartupTest#testAppli...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks: 348419
  Show dependency tree
 
Reported: 2011-05-18 07:58 EDT by Satyam Kandula CLA
Modified: 2019-08-27 10:49 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Satyam Kandula CLA 2011-05-18 07:58:11 EDT
There is ~10% regression in this test (org.eclipse.core.tests.runtime.perf.StartupTest#testApplicationStartup) starting 6th or 7th May. The regression is not really clear. It is seen both on linux and windows. Unfortunately, the windows performance results are not generated, but I could see it in the DB.
Comment 1 Oleg Besedin CLA 2011-05-18 09:36:26 EDT
That's the headless startup test case.
Comment 2 Thomas Watson CLA 2011-05-18 11:28:27 EDT
I'm not seeing the issue start with the 6th or 7th build.  The regression seems consistent before the 6th or 7th.  My suspicion is that this test is invalid because each release we add more bundles and that contributes to the overall startup time.  Headless starts make this more evident because the overhead of starting the framework is pretty much the whole test.
Comment 3 Satyam Kandula CLA 2011-05-25 07:34:25 EDT
Do you plan to do something with this bug?
Comment 4 Thomas Watson CLA 2011-05-25 09:16:54 EDT
(In reply to comment #3)
> Do you plan to do something with this bug?

No, the slowdown can be attributed to the growing number of bundles.
Comment 5 Lars Vogel CLA 2019-08-27 10:49:56 EDT
Bug is getting to too, we have to look again once the performance test are running again.