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.
Filing as a follow-up for issue 130061. The current performance is acceptable for 6.1, but going forward we need to rethink the way mapper behaves, as freezing for 4 seconds is still not as good as it could be. Not sure whether it fits with NB's performance guidelines... It does not -- http://performance.netbeans.org/responsiveness/whatisresponsiveness.html
We still looking for ways to improve mapper performance, but this becomes harder and harder as more and more new features are being added to mapper. As soon as we cant keep load time for mapper under 1 sec, we shoulkd povide progress bar or any other feedback telling user about current mapper status. If we move mapper from separate tab to panel, visible under main diagram area, we can take mapper loading process to background thread and use mapper panel to show status, like "Loading mapper..." while this thread is active.
It looks like not P1 priority enhancement of the mapper. The mapper works quite fast with reasonable size of its content. The bigger content, the more time it takes to load. And it seems normal. So it is a kind of issue, which never can be fixed because we can create bigger project, which will take too much time to load the mapper.
Well, we have a very good sample of what is "big" -- HL7 schema. How long does it take to load the mapper with this schema? Anyways, it is a P1, until we have a progress bar which would tell the user that the mapper has not hung, but is just loading the schemas. See Alexey's comment above, it is fair enough.