Bug 270201 - [model] ExternalFoldersManager is a performance bottleneck
Summary: [model] ExternalFoldersManager is a performance bottleneck
Status: VERIFIED DUPLICATE of bug 313153
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.6.1   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2009-03-26 22:11 EDT by Min Idzelis CLA
Modified: 2011-05-16 03:26 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Min Idzelis CLA 2009-03-26 22:11:38 EDT
Build ID: Eclipse 3.5

Steps To Reproduce:
The refreshJob in #refrehReferences() is causing a performance bottleneck. This is because if a lot (50+) of Java Projects were created in a IWorkspaceRunnable that ran with a ws-root scheduling rule, all the notifications are sent at the end. After the notifications are sent, this refresh job is scheduled (with no scheduling rule). The refresh() method automatically acquires the refreshRule(). Since the job was scheduled without a rule, it starts running right away and occupies a thread while it is waiting for the rule to be ready. 

It would be much better if there was just a single job refreshed all external folders. This way, only a single thread at most will be created. 

More information:
Comment 1 Olivier Thomann CLA 2011-03-15 11:36:49 EDT
I believe this has been fixed.
Jay, please check if this is still an issue.
Comment 2 Jay Arthanareeswaran CLA 2011-03-16 01:24:11 EDT
Yes, this is has already been fixed by bug #313153.

*** This bug has been marked as a duplicate of bug 313153 ***
Comment 3 Satyam Kandula CLA 2011-05-16 02:17:35 EDT
Verified for 3.7 RC1 using build I20110512-2000
Comment 4 Ayushman Jain CLA 2011-05-16 03:26:44 EDT
Verified for 3.7RC1 using build I20110514-0800. (Steps given in bug 313153)