This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41626 - 1st form opening is slow
Summary: 1st form opening is slow
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Jan Stola
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-04-02 11:58 UTC by _ rkubacki
Modified: 2006-03-24 10:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
gzipped tar archive with form used for testing (5.11 KB, application/octet-stream)
2004-04-02 12:00 UTC, _ rkubacki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2004-04-02 11:58:38 UTC
build 200404011800, JDK1.5.0b45, Linux RH, 800MHz,
512MB

First form opening is very slow. I mean even in
case when there is already some Java editor opened
it can take >10s to complete form opening. During
this time Jave editor is opened in less than 2
seconds and the rest of time is spent by form
opening for a not too big form that I used.

I know that we already spent a lot of time trying
to fix this but probably it is no enough. Some
related issues are #27183, #39036, #39037.
Comment 1 _ rkubacki 2004-04-02 12:00:59 UTC
Created attachment 14254 [details]
gzipped tar archive with form used for testing
Comment 2 _ rkubacki 2004-04-02 12:23:26 UTC
Maybe there is a possibility to improve UI with multiview editors that
can help to get better behaviour.
Comment 3 Jan Stola 2004-07-02 10:24:48 UTC
We have improved the first form opening:

- multiview has been introduced => only active element
  (Java or Form) is loaded/initialized after Edit/Open
- loading of palette items has been rewritten to use
  SAX instead of DOM
- usage of source hierarchy is avoided during form loading;
  JMI is used instead

The first form opening is still significantly slower than
the subsequent ones, because some one-time activities must
be performed:
- form and core/multiview module classes are loaded and initialized
- properties, i18n, i18n/form module classes are loaded
  (if the form uses i18n/form module features like in your example)
- a lot of classes are introspected, bean infos are loaded
- form editor settings are deserialized
- form group (Component Palette and Inspector) are created
- the content of component palette is loaded
...

By the way the comparsion with the Editor is irrelevant. The Editor
"displays some text" and performs other activities (like parsing)
after that. Unfortunately much more must be finished before form
editor is able to show something resonable.
Comment 4 Marek Grummich 2005-07-11 14:22:35 UTC
verified