Reparsing of files during project open in Diana

When I reopen an existing project, Diana seems to reindex every single
file in the project again, and it takes absolutely ages to be able to
start working. Is this expected?

N.

9 comments
Comment actions Permalink

Hello Nathan,

When I reopen an existing project, Diana seems to reindex every single
file in the project again, and it takes absolutely ages to be able to
start working. Is this expected?


No. Are there any exceptions?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dmitry,

Dmitry Jemerov wrote:
>> When I reopen an existing project, Diana seems to reindex every single
>> file in the project again, and it takes absolutely ages to be able to
>> start working. Is this expected?


No. Are there any exceptions?

None that I can see... I guess the only thing left to try is clearing
the cache out... unless you have any other suggestions?

N.

0
Comment actions Permalink

I see the same thing!

Whenever I change any setting in a module I see the whole index process kick
off again. It's definitely not re-indexing everything but it seems to "scan"
files to index every time I change anything in a module config.

I also see this when I open up projects.


"Dmitry Jemerov" <yole@jetbrains.com> wrote in message
news:63d8c2ccb16998cad5d30791b4c2@news.jetbrains.com...

Hello Nathan,

>
>> When I reopen an existing project, Diana seems to reindex every single
>> file in the project again, and it takes absolutely ages to be able to
>> start working. Is this expected?
>

No. Are there any exceptions?

>

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

>


0
Comment actions Permalink

Hello Grant,

I see the same thing!

Whenever I change any setting in a module I see the whole index
process kick off again. It's definitely not re-indexing everything but
it seems to "scan" files to index every time I change anything in a
module config.


This is actually expected. We hope that we'll be able to optimize this before
the final release.

How long does this "Searching for files to index" process take for you?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Well, I have the same problem, and it's new in IntelliJ 8 (it never happened in 7, or it was not visible). It's quite annoying, and sometimes it takes a long (15+ seconds) time, which makes it even more annoying.

0
Comment actions Permalink

For me it'll take a good 25 seconds. I have a very large project (85
modules) and I'm including most of the WAS 6.1 jar fileset since I'm
leveraging their JMS/J2EE/JAVA libraries. In addition I have quite a few
other libraries being included. It seems that the scanner is scanning the
jars associated to the libraries as well even though I haven't changed any
jar references.


"Dmitry Jemerov" <yole@jetbrains.com> wrote in message
news:63d8c2ccb17a98cad64e6dcc4df8@news.jetbrains.com...

Hello Grant,

>
>> I see the same thing!
>>
>> Whenever I change any setting in a module I see the whole index
>> process kick off again. It's definitely not re-indexing everything but
>> it seems to "scan" files to index every time I change anything in a
>> module config.
>

This is actually expected. We hope that we'll be able to optimize this
before the final release.

>

How long does this "Searching for files to index" process take for you?

>

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

>


0
Comment actions Permalink

I just saw this when reopening a project I had closed a few minutes earlier. I checked the log, and there are no exceptions in there.

I will clean my cache out and watch for it again.

0
Comment actions Permalink

Observing the same behavior. Cleaning caches doesn't change it. E.g. modify any setting of the module in the existing project, hit Ok, and watch it scan for changes. No actual reindexing takes place, but the search takes time for large projects (and that's what we poor sods are mostly working on ;)

Here's the first point of attack: it starts with JDK rescanning, which is totally insane, see if jdk change can be detected in the settings dialog and then made optional during the search for changes.

HTH,
Andrew

0
Comment actions Permalink

I've noticed that it also re-scans all XML/XSL/XSD files, which is a royal pain since we have thousands of stylesheets and schemas!

0

Please sign in to leave a comment.