A participant commented that scanning of classpath takes too long. He mentioned that in Eclipse it's faster.
Compare our classpath scanning to Eclipse. Maybe it's just a perception of slow progress because when the classpath is scanned the very first time it blocks
opening of the first project, so it looks like the whole IDE is stuck for a while.
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
Now it should be much better, see mesurements (up-to-date checking section):
Feel free to try my library, FastClasspathScanner, to improve classpath scanning speed -- it is parallelized and highly optimized:
I would be curious to see benchmarks comparing the updated NetBeans scanner and Eclipse to FastClasspathScanner.