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 194959 - 7s in org.netbeans.modules.project.ui.ProjectUtilities.openProjectFiles()
Summary: 7s in org.netbeans.modules.project.ui.ProjectUtilities.openProjectFiles()
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-02-01 16:19 UTC by adam_myatt
Modified: 2012-11-08 08:29 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 162188

Attachments
nps snapshot (64.62 KB, application/nps)
2011-02-01 16:19 UTC, adam_myatt 		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 adam_myatt 2011-02-01 16:19:28 UTC 
Build: NetBeans IDE 7.0 Beta (Build 201011152355)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP

User Comments:
adam_myatt: opening a java web app project after the IDE had been open for an hour with no other projects open.

mrpc: First Startup in windows 7

GUEST: It happened when I started Netbeans. I have noticed that it is a lot slower than 6.9.1 in general. I hope all this will be fixed soon. I really look forward to a great release. Slow means people will switch.

marcotts: opening a java class



Maximum slowness yet reported was 10558 ms, average is 4876
Comment 1 adam_myatt 2011-02-01 16:19:34 UTC 
Created attachment 105557 [details]
nps snapshot
Comment 2 Stanislav Aubrecht 2011-02-02 15:19:36 UTC 
the last snapshot shows that the loading of UI class for tab displayer took 300ms

org.netbeans.ModuleManager$SystemClassLoader.loadClass()

the slowness in other snapshots was cause by slow native disk access, nothing fixable on netbeans side.

reassigning to module system for evaluation of the last snapshot.
Comment 3 Jaroslav Tulach 2011-04-15 11:20:22 UTC 
Stando, 300ms in loading a class is not that much. Definitely not a reason for a slowness report. The problem is that 

org.netbeans.modules.project.ui.ProjectUtilities.openProjectFiles() opens six files at once while being in AWT.

As far as I know Openable.open()/Editable.edit() can be called from any thread. It does not have to be called from AWT. That would be my primary fix.

Another fix is to using six independent EventQueue.invokeLater. Each of them would then take less then 1s, which is OK.

Anyway moving to projectui.
Comment 4 Petr Cyhelsky 2012-11-08 08:29:01 UTC 
Last slowness report is from 7.0 Beta2 - doesn't seem to be a problem now