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 191463 - Project scanning extremely slow
Summary: Project scanning extremely slow
Status: RESOLVED INCOMPLETE
Alias: None
Product: php
Classification: Unclassified
Component: Navigation (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P1 normal with 1 vote (vote)
Assignee: Petr Pisl
URL:
Keywords: PERFORMANCE, REGRESSION
Depends on:
Blocks:
 
Reported: 2010-10-29 11:47 UTC by tln
Modified: 2011-06-27 11:56 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tln 2010-10-29 11:47:07 UTC
PHP Project with:
- 1055 Classes (1 per file)
- 241 Interfaces (1 per file)
- 282 Other PHP Files
- all directories containing binary files are excluded in Options->Misc->Files->Ignored Files Pattern.

NetBeans 7.0:
- Initial scan of the project: 20 (!) minutes
- Code Assist: sometimes 4-7 seconds, sometimes no response except "Please wait..." message; NetBeans asks me to report problem

NetBeans 6.9.1:
- Initial scan of the project: 11 (!) minutes
- Code Assist: sometimes 7 seconds, sometimes no response except "Please wait..." message

NetBeans 6.8 (same project, same code assist):
- Initial scan of the project: 30 seconds
- Code assist: 0.5 seconds


It does not matter much which kind of code assist is requested. The behaviour is very consistent, even if no complex knowledge is required to do the code assist (for instance when suggesting a namespace).


We'll have to continue using 6.8, although it is also starting to be annoying for seemingly scanning only the first 1000 classes it finds so that increasingly large parts of our project are not navigatable. Especially in a big project this is a serious limitation.


We'd be very happy if you could fix that because for everything else NetBeans is just the perfect IDE for us.

(In order to save you time and effort perhaps you could optionally offer the 6.8 scanning algorithm again, just without the 1000 classes limitation. Except that limitation it was perfect for our needs.)
Comment 1 Marian Mirilovic 2011-05-18 20:30:02 UTC
Nice measurement, thanks a lot for data ... we will look at this for NB 7.1
Comment 2 Tomas Mysik 2011-06-01 20:17:15 UTC
Reporter, could we have your project? If not, could you please create one or two profiler snapshot(s) [1] for, let's say, one minute of the scanning? That would help us a lot.

Thanks in advance.
[1] http://wiki.netbeans.org/FitnessViaPartnership
Comment 3 Petr Pisl 2011-06-27 11:56:58 UTC
I'm marking this issue as incomplete due to we don't have a snapshot. Please provide a snapshot as Tomas wrote and reopen the issue. 

I have created test project that contains more classes as reporter mentioned and the behavior is much faster.