Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349221 - Should system parts be loaded/cached lazily?
Summary: Should system parts be loaded/cached lazily?
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-13 14:50 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:19 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 Justin Spadea CLA 2011-06-13 14:50:10 EDT
Right now all bindings for the system parts are cached immediately, and this takes tens of seconds to finish (causing the first operation that references a compiler's system environment to wait until it completes). This is done so that you can reference functions, fields, libraries, etc without needing imports or qualifications. For performance it might make sense to enable lazy loading while maintaining current behavior.
Comment 1 Paul Harmon CLA 2011-09-12 08:18:32 EDT
This is now done on demand.
Comment 2 Justin Spadea CLA 2011-09-13 15:58:01 EDT
Paul - this isn't really done in the way I meant. While SystemEnvironment.initializeSystemPackages() is called the first time the system environment is needed, it's still deserializing all the IRs up front which is the majority of the init time. This enhancement was meant to only deserialize a part when it's actually needed.
Comment 3 Lisa Lasher CLA 2011-11-04 11:45:34 EDT
Closing this work item