Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339194 - [builder] Improve caching during analyzation phase
Summary: [builder] Improve caching during analyzation phase
Status: CLOSED FIXED
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: 1.0.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 05:44 EST by Karsten Thoms CLA
Modified: 2013-02-21 08:09 EST (History)
0 users

See Also:
karsten.thoms: indigo+

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 Karsten Thoms CLA 2011-03-08 05:44:47 EST 
The XtendXpandBuilder lacks performance especially with growing project size. The performance can become totally unnacceptable when the workspace has many resources and the analyzation strategy is configured to analyze the whole project.

Reason is that Xtend files are analyzed multiple times. Also the cache "allExtensionPerResource" from ExecutionContextImpl does not work, since the cache will be filled within a cloned ExecutionContext and the cached information gets lost when the scope of the cloned context is left.

To solve this problem there should be a BuildState object that is used as a cache for already analyzed resources during a build. This BuildState will be set as global variable to the XpandPluginExecutionContext when the builder starts analyzing a project.
Comment 1 Karsten Thoms CLA 2011-03-08 07:33:55 EST 
Committed with a418dd0ce60bc8db9fbf6269155689d213903ffb
Comment 2 Karsten Thoms CLA 2013-02-21 08:09:22 EST 
Bug resolved before Xpand 1.2 release date => Closing