Bug 337950 - [perfs] Regression in SeparateVMTests and OpenAntEditor tests
Summary: [perfs] Regression in SeparateVMTests and OpenAntEditor tests
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Pradeep Balachandran CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks: 348419
  Show dependency tree
 
Reported: 2011-02-23 05:07 EST by Satyam Kandula CLA
Modified: 2019-08-27 10:50 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Satyam Kandula CLA 2011-02-23 05:07:03 EST 
There is about 40-70% performance regression in the  org.eclipse.ant.tests.ui.editor.performance.SeparateVMTests and around 10% regression in OpenAntEditor. This is first seen on 12th Feb.
Comment 1 Michael Rennie CLA 2011-04-14 16:26:38 EDT 
The regression began once the update to Ant 1.8.2 went live.

I was expecting a bit of a dip in the editor performance as we changed the caching scheme to not hold onto a huge DOM object, and in doing so we incur a slight bit more processing which accounts for the few extra milliseconds extra.

I am still looking into the separate VM regression. We made some changes to do extra work cleaning up after and during launches to avoid the incremental OOME problem we have been plagued with (bug 130545), but I have no hard evidence yet was is causing such a large regression.
Comment 2 Dani Megert CLA 2011-06-03 05:03:00 EDT 
Ping.
Comment 3 Curtis Windatt CLA 2011-06-03 16:43:58 EDT 
No changes are planned here for 3.7, moving to 3.8 for now.
Comment 4 Michael Rennie CLA 2012-03-01 15:03:55 EST 
no changes planned here for 3.8 either. We can compare the performance change when we update to Ant 1.8.3 as well.
Comment 5 Lars Vogel CLA 2019-08-27 10:50:12 EDT 
Bug is getting to too, we have to look again once the performance test are running again.