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.
Summary: | Classpath scanning takes too long | ||
---|---|---|---|
Product: | java | Reporter: | jrojcek <jrojcek> |
Component: | Source | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | issues |
Priority: | P2 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://ui.netbeans.org/usability/editor_2/report.html | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | 140680 | ||
Bug Blocks: |
Description
jrojcek
2007-06-26 15:20:58 UTC
The speed of initial scan was improved from the time of UI study. We did a comparison to Eclipse - it is really faster. We talked both about how to improve the raw performance of the scanning as well as how to improve the user experience during the scanning. Let's keep this issue to track the raw performance improvements. One idea was to optimize disk touches when comparing source file time stamps with cached files. This should help after the cold start (i.e. files touched for the first time). There should be more space for improvements - just needs more investigation. Now it should be much better, see mesurements (up-to-date checking section): http://wiki.netbeans.org/JavaScanDesc Feel free to try my library, FastClasspathScanner, to improve classpath scanning speed -- it is parallelized and highly optimized: https://github.com/lukehutch/fast-classpath-scanner I would be curious to see benchmarks comparing the updated NetBeans scanner and Eclipse to FastClasspathScanner. |