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 217235 - LowPerformance took 26240 ms.
Summary: LowPerformance took 26240 ms.
Status: RESOLVED FIXED
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.3
Hardware: All All
: P2 normal (vote)
Assignee: Petr Pisl
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-08-22 14:15 UTC by Exceptions Reporter
Modified: 2012-11-14 15:52 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 191744


Attachments
nps snapshot (128.00 KB, application/nps)
2012-08-22 14:15 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2012-08-22 14:15:02 UTC
This bug was originally marked as duplicate of bug 200233, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201208220001)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b06
OS: Windows 7

User Comments:
GUEST: I just opened a project (it's quite big)
For some reason since I installed NetBeans, it just runs slow.



Maximum slowness yet reported was 26240 ms, average is 26240
Comment 1 Exceptions Reporter 2012-08-22 14:15:11 UTC
Created attachment 123406 [details]
nps snapshot
Comment 2 Petr Pisl 2012-08-30 15:08:48 UTC
Both reports shows problems in 

org.netbeans.modules.parsing.spi.indexing.support.IndexResult.getUrl()	
and
org.openide.filesystems.URLMapper.findFileObject()

which takes more then 80% of the long time.

Are your sources on local drive or a net drive?
Comment 3 padraigdoran 2012-08-30 16:48:01 UTC
@Petr, the source files are on my main C: drive, along with Netbeans too.
Comment 4 Petr Pisl 2012-08-31 09:15:22 UTC
@padraigdoran: Thanks. Could you describe more. Can you see the slownest during editing? Or just during indexing?
Comment 5 padraigdoran 2012-08-31 09:26:44 UTC
(In reply to comment #4)
> @padraigdoran: Thanks. Could you describe more. Can you see the slownest during
> editing? Or just during indexing?

I remember scrolling the Navigator window of a JavaScript file and it just got slow. When I turned off the "show non public members" button on the bottom of the Navigator window, it was fast again. With the "show non public members" button turned on, lots of expandable trees of Anonym$n appear and this seems to slow it down a lot.
Comment 6 Petr Jiricka 2012-09-12 12:47:53 UTC
This sounds important to be fixed for final release, but does not sounds like a beta stopper (3 reports so far). Changing priority to P2.
Comment 7 Petr Pisl 2012-10-31 15:45:11 UTC
I will remove the anonymous object from the navigator. It should help. When you switch off the navigator at all, the problem disappear completely?
Comment 8 padraigdoran 2012-10-31 18:32:51 UTC
(In reply to comment #7)
> I will remove the anonymous object from the navigator. It should help. When you
> switch off the navigator at all, the problem disappear completely?

With the navigator switched off, then there is no slow down at all
Comment 9 Petr Pisl 2012-11-14 15:52:38 UTC
ER 624569: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 624324: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 623509: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 623316: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 620705: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 620069: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 619704: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 619564: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 617917: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()
ER 617544: o.n.m.javascript2.editor.index.JsIndex.getGlobalVar()

...

The issue with getGlobalVar was fixed last week. Also I have eliminate anonymous literar objects from the navigator. Only remaining issue is, that navigator is refreshing too much after a change in editor. I created new issue for it: #222130.

After this all I close this issue as fixed.