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.
Created attachment 107926 [details] using 77% of the CPU I have a huge Multi-Projects Maven project. Scanning projects... is stopping with at one project und only consumes one CPU with 100%. The profiler shows that org.netbeans.modules.maven.embedder.MavenEmbedder.getSettings() uses 68% of the time and org.netbeans.modules.projectapi.SimpleFileOwnerQueryImplementation.getOwner()uses 22%.
Created attachment 107927 [details] getOwner 22% of the CPU
Do you have the original *.nps file? That would be more useful to attach than screenshots. Excessive calls to getSettings can probably be fixed. Other problems may remain. I do not know how big "huge" is, but you are probably better off opening only a few modules of interest (uncheck "Open Required Projects"!) unless you really mean to e.g. do a system-wide rename refactoring among SNAPSHOT dependencies. If the sources are publicly available, let me know as they might be a useful test case.
core-main #f7a0fbb66aec may help.
Integrated into 'main-golden', will be available in build *201104280000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/f7a0fbb66aec User: Jesse Glick <jglick@netbeans.org> Log: #198047: cache result of loading settings.xml (unless it changes) to save time opening/parsing projects.
Ok hughe for me. around 30 Maven modules with 11000 .java Files.
Received the *.nps privately. Based on that, I believe f7a0fbb66aec should reduce overhead considerably. I added another smaller optimization in core-main #603117af867f.
Integrated into 'main-golden', will be available in build *201105050000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/603117af867f User: Jesse Glick <jglick@netbeans.org> Log: #198047 cont'd: skip straight to MavenFileOwnerQueryImpl for artifact ownership; SimpleFileOwnerQueryImplementation would not generally produce results anyway.
this bug is fixed. checked with the nightly build.
Excellent, thanks for following up.