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.
This bug report is based on the VWP performance tiger team observation. When a complex page is loaded in to the designer, it becomes very cumbersome to design the page. While moving around the components or modifying the component properties it takes several second for the designer to repaint. Designer freezes for several seconds On a fast machine it takes about 7-10 seconds for designer refresh. On a slow end machine, it takes about 30-40 seconds on a very complex page. We analyzed the performance using The main culprit seems to be org.apache.batik.css.engine.CSSEngine.getCascadedStyleMap. (see attachments). For every property change in the component the StyleMap is recomputed by batik parser which is the main performance bottle neck. Even when one property changes other computed properties in the parents and children (inheritance + cascading) might change. so most of the things get recomputed after that. Is there a way not to do page layout when modifications made to properties which does not influence the layout at all (e.g renaming the id) or doing a binding that does not change the visual at all.
Created attachment 43740 [details] Call tree for designer painting performance
Created attachment 43748 [details] Designer painting hot spots
Created attachment 43756 [details] Sample Project
Also refer bug http://www.netbeans.org/issues/show_bug.cgi?id=105179
OK, it seems it is the same issue, making it a duplicate. *** This issue has been marked as a duplicate of 105179 ***