[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Startup performance / Lazy creation of editors.
|
Detailed profiling of startup time has been done to find where the hotspots
are. The contents of the plugin.xml files are cached, and this cache takes
about 200ms to read for a full install of the Eclipse SDK. If plugin.xml
files have been added, removed or modified (not the usual case), a full
parse and resolve takes about 3 seconds.
You can get a breakdown of startup time by plugin by adding the following
flags to your .options file and running eclipse with "-debug". The only
thing that is not included in those times is instantiating and restoring
the UI content. If you subtract the various plugin startup times from the
total startup time, you'll see that restoring the UI takes a large
percentage of the total startup time.
org.eclipse.core.runtime/debug=true
org.eclipse.core.runtime/timing/startup=true
"Bob Foster"
<bob@xxxxxxxxxx> To: <platform-ui-dev@xxxxxxxxxxx>
Sent by: cc:
platform-ui-dev-admin@ Subject: Re: [platform-ui-dev] Startup performance / Lazy
eclipse.org creation of editors.
05/01/2002 03:40 AM
Please respond to
platform-ui-dev
Of course, all this assumes that opening editors on startup is a problem.
Versus, say, reading the plugin.xml files, etc. It would be interesting to
see a breakdown.
Bob
