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 116936 - time for Adding Table Component exceeds boundary
Summary: time for Adding Table Component exceeds boundary
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: _ sandipchitale
URL:
Keywords: PERFORMANCE
: 116808 (view as bug list)
Depends on: 123532 123536
Blocks:
  Show dependency tree
 
Reported: 2007-09-27 12:32 UTC by Oleg Khokhlov
Modified: 2008-01-30 05:10 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
JProfiler screen shot for first table drop (258.86 KB, application/octet-stream)
2007-10-03 22:12 UTC, _ deva 		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 Oleg Khokhlov 2007-09-27 12:32:53 UTC 
Adding Table Component [1]	7073  ms	1000  ms
Adding Table Component [2]	7116  ms	1000  ms
Comment 1 _ deva 2007-10-03 22:11:48 UTC 
On my windows XP(T2500 duo core 2 GHz/2GB RAM) it takes about 7-8 seconds for the first drop and about 2 seconds for 
the second drop.
Comment 2 _ deva 2007-10-03 22:12:36 UTC 
Created attachment 50144 [details]
JProfiler screen shot for first table drop
Comment 3 _ deva 2007-10-03 22:14:46 UTC 
As per the attached screen shot, about 50% time is spent in designer code. Therefore re-assigning to Peter for his 
evaluation.
Comment 4 _ sandipchitale 2007-10-04 06:31:14 UTC 
Asking for waiver.
Comment 5 Peter Zavadsky 2007-10-04 18:45:25 UTC 
It is only about 30% of time spent in the desinger, I believe the slowest part in that is the computing the styles,
which can't be improved more without comprehensive rewrite (the problematic batik usage). That is already known.

Note the DesignerPaneDropTarget.drop, at the end delegates to insync to create the component bean (etc.),
also the DomSynchronizer spents the time calling the renderer, don't count that as a designer code.
The rest (70%)  is somewhere else.

Passing back.
Comment 6 _ sandipchitale 2007-10-08 17:37:50 UTC 
No objections in 48 hours.
Comment 7 _ sandipchitale 2007-10-28 02:47:24 UTC 
*** Issue 116808 has been marked as a duplicate of this issue. ***
Comment 8 _ sandipchitale 2008-01-14 20:50:56 UTC 
The implementation of the following two issues may help this scenario:

123532
123536

Need to do the measurement after the two are completed.
Comment 9 _ sandipchitale 2008-01-30 05:10:09 UTC 
All the know work on performance has been done.
Comment 10 _ sandipchitale 2008-01-30 05:10:45 UTC 
All the know work on performance has been done.