Demetra and JSP file indices...

Building JSP Files indices - this is a new dialog I am seeing on loading a project and demetra is spinning for quite a while (more than 10 mins for my project).

I can guess what this is - but is there a way to disable this?

thanks
vinay

11 comments

Hello Vinay,

After next EAP JSP files indices will be built only on first opening of a
project, is it enough for you?
There is no way to disable this because it is required for the context-dependent
resolving in JSP (IDEADEV-4482).

BTW, how many JSP files do you have in your project?

Building JSP Files indices - this is a new dialog I am seeing on
loading a project and demetra is spinning for quite a while (more than
10 mins for my project).

I can guess what this is - but is there a way to disable this?

thanks
vinay

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

total 2664 JSP totalling 281161 lines

By first opening - do you mean the first time in the life cycle of the project - or the first time every time I open the project? Right now it seems to do every time I open the project but also on frame switch, ctrlAlty, save etc.

0

I'm coming in late on this, but why can't this stuff happen in the background?

I've complained about this before with IDEA, a lot of things seem to be in
modal dialogs that can be moved to the background while we do other stuff.

R
(ps sorry if my first comment in a very long time is a complaint :) )

Hello Nikolay,

NC> Hello Vinay,
NC>
NC> After next EAP JSP files indices will be built only on first opening
NC> of a
NC> project, is it enough for you?
NC> There is no way to disable this because it is required for the
NC> context-dependent
NC> resolving in JSP (IDEADEV-4482).
NC> BTW, how many JSP files do you have in your project?
NC>
>> Building JSP Files indices - this is a new dialog I am seeing on
>> loading a project and demetra is spinning for quite a while (more
>> than 10 mins for my project).
>>
>> I can guess what this is - but is there a way to disable this?
>>
>> thanks
>> vinay
NC> ---
NC> Nikolay Chashnikov
NC> Software Developer
NC> JetBrains, Inc
NC> http://www.jetbrains.com
NC> "Develop with pleasure!"


0

Hello Vinay,

I mean that these indices are built on the first opening your project in
Demetra and then are saved on disk so on a subsequent opening of your project
IDEA will merely load it instead of build again.

Rebuilding indices on frame switch, save, etc is a bug which has been already
fixed.

total 2664 JSP totalling 281161 lines

By first opening - do you mean the first time in the life cycle of the
project - or the first time every time I open the project? Right now
it seems to do every time I open the project but also on frame switch,
ctrlAlty, save etc.

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Hello Robert,

This stuff cannot happen in the background because the mentioned indices
must be built completely before opening any JSP file.

I'm coming in late on this, but why can't this stuff happen in the
background?

I've complained about this before with IDEA, a lot of things seem to
be in modal dialogs that can be moved to the background while we do
other stuff.

R
(ps sorry if my first comment in a very long time is a complaint :) )
Hello Nikolay,

NC>> Hello Vinay,
NC>>
NC>> After next EAP JSP files indices will be built only on first
NC>> opening
NC>> of a
NC>> project, is it enough for you?
NC>> There is no way to disable this because it is required for the
NC>> context-dependent
NC>> resolving in JSP (IDEADEV-4482).
NC>> BTW, how many JSP files do you have in your project?
>>> Building JSP Files indices - this is a new dialog I am seeing on
>>> loading a project and demetra is spinning for quite a while (more
>>> than 10 mins for my project).
>>>
>>> I can guess what this is - but is there a way to disable this?
>>>
>>> thanks
>>> vinay
NC>> ---
NC>> Nikolay Chashnikov
NC>> Software Developer
NC>> JetBrains, Inc
NC>> http://www.jetbrains.com
NC>> "Develop with pleasure!"
---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

And why don't you block the opening of any JSP file until the index
build has finished in the background? Meanwhile one could work on Java
files or whatever else.

Nikolay Chashnikov wrote:

Hello Robert,

This stuff cannot happen in the background because the mentioned indices
must be built completely before opening any JSP file.

>> I'm coming in late on this, but why can't this stuff happen in the
>> background?
>>
>> I've complained about this before with IDEA, a lot of things seem to
>> be in modal dialogs that can be moved to the background while we do
>> other stuff.
>>
>> R
>> (ps sorry if my first comment in a very long time is a complaint :) )
>> Hello Nikolay,
>>

NC>> Hello Vinay,
NC>> NC>> After next EAP JSP files indices will be built only on first
NC>> opening
NC>> of a
NC>> project, is it enough for you?
NC>> There is no way to disable this because it is required for the
NC>> context-dependent
NC>> resolving in JSP (IDEADEV-4482).
NC>> BTW, how many JSP files do you have in your project?

>>>> Building JSP Files indices - this is a new dialog I am seeing on
>>>> loading a project and demetra is spinning for quite a while (more
>>>> than 10 mins for my project).
>>>>
>>>> I can guess what this is - but is there a way to disable this?
>>>>
>>>> thanks
>>>> vinay

NC>> ---
NC>> Nikolay Chashnikov
NC>> Software Developer
NC>> JetBrains, Inc
NC>> http://www.jetbrains.com
NC>> "Develop with pleasure!"
---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0

Hello Martin,

I think that building the indices in the background may greatly slowdown
IDEA. Besides these indices are built only on first opening of a project
(starting with next EAP). IMO the game is not worth the candle.

And why don't you block the opening of any JSP file until the index
build has finished in the background? Meanwhile one could work on Java
files or whatever else.

Nikolay Chashnikov wrote:

>> Hello Robert,
>>
>> This stuff cannot happen in the background because the mentioned
>> indices must be built completely before opening any JSP file.
>>
>>> I'm coming in late on this, but why can't this stuff happen in the
>>> background?
>>>
>>> I've complained about this before with IDEA, a lot of things seem to
>>> be in modal dialogs that can be moved to the background while we do
>>> other stuff.
>>>
>>> R
>>> (ps sorry if my first comment in a very long time is a complaint :)
>>> )
>>> Hello Nikolay,
>> NC>> Hello Vinay,
>> NC>> NC>> After next EAP JSP files indices will be built only on
>> first
>> NC>> opening
>> NC>> of a
>> NC>> project, is it enough for you?
>> NC>> There is no way to disable this because it is required for the
>> NC>> context-dependent
>> NC>> resolving in JSP (IDEADEV-4482).
>> NC>> BTW, how many JSP files do you have in your project?
>>>>> Building JSP Files indices - this is a new dialog I am seeing on
>>>>> loading a project and demetra is spinning for quite a while (more
>>>>> than 10 mins for my project).
>>>>>
>>>>> I can guess what this is - but is there a way to disable this?
>>>>>
>>>>> thanks
>>>>> vinay
---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

For now I have added my web/jsp folder to excluded folders list to make things better.

Do you think - you can have a command line interface to JSP indexing - that way - I can fire it up once (possibly add to my cvs checkout ant script) and not pay the tax again.

Also, I am not sure if the JSP indexing is causing huge memory overhead - but my footprint for 5131 is about 150M bigger than for 5.1 Most of the time, EAPs start with higher footprint till the optimizations come in - but just wondering if the JSP indexing could be hurting the footprint quite a bit.

0

Hello Vinay,

I think that a command line interface to JSP indexing make no sense because
it will be performed once (on first opening your project in Demetra) starting
with next EAP.

For now I have added my web/jsp folder to excluded folders list to
make things better.

Do you think - you can have a command line interface to JSP indexing -
that way - I can fire it up once (possibly add to my cvs checkout ant
script) and not pay the tax again.

Also, I am not sure if the JSP indexing is causing huge memory
overhead - but my footprint for 5131 is about 150M bigger than for 5.1
Most of the time, EAPs start with higher footprint till the
optimizations come in - but just wondering if the JSP indexing could
be hurting the footprint quite a bit.

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

> Also, I am not sure if the JSP indexing is causing huge memory
overhead - but my footprint for 5131 is about 150M bigger than for 5.1
Most of the time, EAPs start with higher footprint till the
optimizations come in - but just wondering if the JSP indexing could be
hurting the footprint quite a bit.

We've had SO many changes in the core, so that it might be anything.
Don't blame the feature for committing all the possible sins, just
because you don't like it, or it has some bugs in the implementation :)

0

as I said
"Most of the time, EAPs start with higher footprint till the
optimizations come in"

it's not that I don't like the feature in princinple - I am just looking for some ideas that might help me reduce the footprint and make development pleasure during the EAP cycle.

peace :)

0

Please sign in to leave a comment.