WindowSystemPersistenceSimplified

(Difference between revisions)
(Less Classloading in EDT)
(Less Classloading in EDT)
Line 21: Line 21:
* ProgressVisualizerProvider.getStatusLineElement() 231 ms
* ProgressVisualizerProvider.getStatusLineElement() 231 ms
-
It's probably good idea to keep the creation of visual components in EDT. But it can be rescheduled to some later moment when the main IDE window is already showing.
+
SA: It's probably good idea to keep the creation of visual components in EDT. But it can be rescheduled to some later moment when the main IDE window is already showing.
[[Category:Performance:Planning]]
[[Category:Performance:Planning]]

Revision as of 16:05, 27 March 2013

Issue 227672 shows that persistence of window system is significantly slowing down the start of NetBeans IDE. According to attachment of Issue 227672:

  • It takes 9.5s to load the whole system and show main window
  • There is 4.7s between main window initialized and window system loaded messages
  • It takes more than 1.5s to show the main window.

How can the time be improved.

Better Deserialization

Why six CloneableTopComponents needs to be loaded! Probably only one of them was visible. Modify the system to deserialize only visible components.

SA: Almost all editors are deserialized to fill 'recent view list' for Ctrl+Tab switcher. Should be easily fixable.


About 4s is spend in XMLSettingsSupport.realSerial. Replacing deserialization with @ConvertAsProperties would improve the time.

Less Classloading in EDT

  • editor.impl.StatusLineFactories$LineColumn.getStatusLineElement() - 335 ms
  • ProgressVisualizerProvider.getStatusLineElement() 231 ms

SA: It's probably good idea to keep the creation of visual components in EDT. But it can be rescheduled to some later moment when the main IDE window is already showing.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo