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 206967 - Scanning groovy project extremely slow
Summary: Scanning groovy project extremely slow
Status: RESOLVED DUPLICATE of bug 180230
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 05:05 UTC by waynezhang
Modified: 2012-01-06 10:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log file (16.24 KB, text/plain)
2012-01-06 05:05 UTC, waynezhang
Details
Project scan summary (16.85 KB, text/plain)
2012-01-06 05:21 UTC, waynezhang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description waynezhang 2012-01-06 05:05:29 UTC
Created attachment 114678 [details]
log file

Scan groovy projects source root is extremely slow. Scan binary/jar is normal.

A log file to scan a unit test source folder with FINE log level attached. It takes about 70s to scan this folder with only 16 source files.

This issue exists on NetBeans version 7.0, 7.0.1 and 7.1 final.

Most time consuming tasks are by indexers org.netbeans.modules.java.source.indexing.JavaCustomIndexer and org.netbeans.modules.groovy.editor.api.GroovyIndexer$Factory.
Comment 1 waynezhang 2012-01-06 05:21:07 UTC
Created attachment 114679 [details]
Project scan summary

To scan a small groovy/grails project with 129 groovy source files and 45 java source files, it took about 20 minutes (1,398,262 ms).
Comment 2 Martin Janicek 2012-01-06 10:23:22 UTC
We are aware of this problem and I'm currently working on it. Would be great if you could provide thread dump, so I'll get some more information.
Comment 3 Martin Janicek 2012-01-06 10:23:39 UTC

*** This bug has been marked as a duplicate of bug 180230 ***