Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 45164 - Performance degradation after Upgrade from Integration to 3.0 M4
Summary: Performance degradation after Upgrade from Integration to 3.0 M4
Status: RESOLVED DUPLICATE of bug 44443
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-18 11:56 EDT by chillum CLA
Modified: 2003-10-29 10:56 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description chillum CLA 2003-10-18 11:56:09 EDT
After moving from the last working integration build (before the M4 release) to
3.0M4, the system became very irresponsive while debugging. 
Moved back to yhe integration build and it started behaving fine. I am worried
that the M4 release has introduced some builds that keep happening in the
backgroud causing this grief. 
I did try to change the machine speed scroller from fast to slow but that did
not help either.
I have moved back and forth between the integration  buil and the release and
the performance changes are obvious every time.
Reverted back to the integrtaion build and have full control on the platform.

System 600 Mhz 384 MB ram.
JDK 1.4.2 on  windows 2000.
Comment 1 John Arthorne CLA 2003-10-20 11:05:43 EDT
Are there specific activities that seem slow, or is it just a general slowness?
 When things are slow, do you notice if the busy indicator in the lower left
corner of the screen is moving?  Is it freezing for long periods without
redrawing the screen, or is it a more uniform degradation?  The more details you
give, the greater chance we have of identifying the problem.

Also, if you work with the task or problem view visible, try turning off its
filters (for example filtering based on selection or working set).  See if this
improves performance.

Can you also give us the build Id of the last integration build that worked ok?
 This information is available under help > about.
Comment 2 John Arthorne CLA 2003-10-20 16:32:01 EDT
Please comment on whether turning off task/problem view filtering fixes the
slowness. I suspect this is another dup of bug 44443.
Comment 3 chillum CLA 2003-10-20 16:40:40 EDT
Version: 3.0.0
Build id: 200309170800
This was the last working integration build before M4.
Debugging / stepping through code became painstakingly slow and using the hot
code replace made it worse. Saartup  of Running the application in debug mode
would take really long to start. 
I deleted the class fiels and built the project again to seeif that had any effect.
I reduced the file size and number fo files for the history that did not help
either.
The yellow progress indicator would keep on be doing something (i think it was
building).
I did have filters set up for the various projects....
Unfortunately I use eclipse as a primary development tool at work and do not
have the flexibility at the current time to go to M4.
Comment 4 John Arthorne CLA 2003-10-29 10:56:43 EST
Marking as dup of 4443.  If you move back to a newer build and have performance
problems that are unrelated to task list filtering, please reopen.

*** This bug has been marked as a duplicate of 44443 ***