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.
| Summary: | time for Adding Table Component exceeds boundary | ||
|---|---|---|---|
| Product: | obsolete | Reporter: | Oleg Khokhlov <ovk> |
| Component: | visualweb | Assignee: | _ sandipchitale <sandipchitale> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | issues, mkhramov |
| Priority: | P2 | Keywords: | PERFORMANCE |
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 123532, 123536 | ||
| Bug Blocks: | |||
| Attachments: | JProfiler screen shot for first table drop | ||
|
Description
Oleg Khokhlov
2007-09-27 12:32:53 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. Created attachment 50144 [details]
JProfiler screen shot for first table drop
As per the attached screen shot, about 50% time is spent in designer code. Therefore re-assigning to Peter for his evaluation. Asking for waiver. 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. No objections in 48 hours. *** Issue 116808 has been marked as a duplicate of this issue. *** The implementation of the following two issues may help this scenario: 123532 123536 Need to do the measurement after the two are completed. All the know work on performance has been done. All the know work on performance has been done. |