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 54503 - Start of profiling can take a while and is blocking AWT thread
Summary: Start of profiling can take a while and is blocking AWT thread
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: iformanek
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-02-03 18:20 UTC by Antonin Nebuzelsky
Modified: 2007-02-12 22:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Event Queue stack trace (1.54 KB, text/plain)
2005-02-03 18:21 UTC, Antonin Nebuzelsky 		Details
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 Antonin Nebuzelsky 2005-02-03 18:20:27 UTC 
When you start profiling of a project (e.g.
Profile Main Project -> Analyze Performance ->
Application Startup -> Run) the execution of
project in profiler is performed in AWT thread.
AWT thread is blocked for many seconds effectively
freezing UI of the whole IDE. This must be changed
to run in a worker thread, using AWT thread only
to update UI when appropriate...
Comment 1 Antonin Nebuzelsky 2005-02-03 18:21:41 UTC 
Created attachment 20184 [details]
Event Queue stack trace
Comment 2 iformanek 2005-02-03 19:52:02 UTC 
Agreed, this is the most important performance issue we are aware of. 
There needs to be work done to clarify what is the exact sequence of 
actions performed during the app startup, and solve it both via 
warmup and offload to RequestProcessor thread.

Also note that the problem seems to be much smaller on subsequent 
profiling runs.
Comment 3 _ rkubacki 2005-02-04 16:54:58 UTC 
What kind of warmup do you mean?
Comment 4 iformanek 2005-02-04 19:21:01 UTC 
The first time the profiling is invoked, a lot of UI needs to be 
created (profiler control panel, results window, big graphs window).
This can be done earlier, e.g. when the Select Task panel is 
disaplayed. I am not talking about IDE startup. Sounds reasonable?
Comment 5 _ rkubacki 2005-02-07 10:09:42 UTC 
Surely.
Comment 6 mishadmitriev 2005-02-10 04:33:34 UTC 
I am willing to investigate this problem once I fix issue 54645.
I agree with Ian that it's likely a problem due to UI elements 
creation and/or massive class load (for instance, I've just 
discovered that jfreechart JAR is nearly 1MB - that's a lot and may 
explain some problems).
Comment 7 Antonin Nebuzelsky 2005-02-14 13:21:39 UTC 
Misha, no need to wait with profiling the profiler. I can point you to
a site-wide licence of a profiler you can use to profile your
profiler. ;o)
Comment 8 iformanek 2005-02-16 09:52:47 UTC 
Reassigning to myself for M6
Comment 9 iformanek 2005-02-24 06:19:25 UTC 
Status update: The start of profiling is no longer performed in AWT 
thread, but it still takes too long, and there are now issues with 
thread synchronization, actions enabling/disabling.
Comment 10 iformanek 2005-03-31 16:01:43 UTC 
The profiler startup no longer blocks AWT, but it still is probably slower than 
necessary and should be looked at. Will file a separate issue for this.
Comment 11 ehucka 2006-10-09 12:10:43 UTC 
Verification of old issues.
Comment 12 Alexander Kouznetsov 2007-02-12 22:06:08 UTC 
Closing old issues.