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.
Build: NetBeans IDE Dev (Build nbms-and-javadoc-6367-on-101222) VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02 OS: Windows 7 User Comments: GUEST: Selecting a propertyfile in the source tree dominiklambrechts: ctrl/alt/f reordening source GUEST: trying to go to variable declaration GUEST: Opening an JFrame Form. Maximum slowness yet reported was 6520 ms, average is 5325
Created attachment 104552 [details] nps snapshot
will evaluate
http://statistics.netbeans.org/exceptions/exception.do?id=336476 was fixed in 7.0 all others are about slow MakeProjectFileOwnerQuery.getOwner caused by spending all the time in call of org.openide.util.lookup.ProxyLookup.lookup
Created attachment 104562 [details] nps snapshot
ProxyLookup is just called too often (Vladimir check the # of invocations it goes to tens). However if we concentrate on the report from Dec 28, then it is clear that org.netbeans.modules.maven.MavenSourcesImpl.checkChanges() calls FileOwnerQuery too much.
(In reply to comment #5) > ProxyLookup is just called too often (Vladimir check the # of invocations it > goes to tens). > > However if we concentrate on the report from Dec 28, then it is clear that > org.netbeans.modules.maven.MavenSourcesImpl.checkChanges() calls FileOwnerQuery > too much. You can go this way and change MavenSourcesImpl, but may be it's time to improve FileOwnerQuery with small cache of owners of already detected files? We have seen that java debugger was improved in times on NFS systems by using cache on own side. Now we again propose to change client's code while I think it's worth to improve speed of ALL clients at once just by improving speed of FileOwnerQuery API itself
A small cache in FOQ seems reasonable.
(In reply to comment #7) > A small cache in FOQ seems reasonable. the crucial part is what invalidates the cache. additionally the MavenSourcesImpl usage of FileOwnerQuery in contains(FileObject) lets me imagine that not one FileObject will be passed all over again, but the method will be fed with many different fileobjects.
Last slowness report is from 7.0 - doesn't seem to be much of a problem now