Focus on large codebases

Hi,
  I have been using IJ for three years and there is a distinct pattern: (a) IJ is great for smaller codebases.   (b) IJ falls flat with large codebases.

I have been trying to use IJ 9.x and 10.X at two internet companies having among the largest codebases in the world.  Eclipse is definitely doing a better job here.  At both companies I ended up relegating IJ to a secondary role since it could not deal with the codebases .

Here are some symptoms:

  • indexing taking forever. Sometimes completing in tens of minutes, other times have to kill after hour/(s)
  • index getting corrupted most times that IJ is shutdown and restarted
  • No option to turn off indexing (yes sometimes I want that..)
  • "Excluded directories" configured in the Project Module Settings dialog not "sticking" -- so IJ ends up indexing areas that I don't want.



These are just some of the issues.


Basically I want to ask the Jetbrains folks:  it's great to go and support a lot of new languages, sure.. but please put more focus on supporting large codebases.

5 comments
Comment actions Permalink

Just curious: do you rate IntelliJ IDEA as large or small code base?

0
Comment actions Permalink

Hi
We spent significant amount of work for supporting large codebases in
IntelliJ IDEA 11 (already available as EAP) so we are eagerly looking
forward for feedback.
Btw, IntelliJ IDEA 10.5.1+ running on JDK 64bit also index code large
codebases much faster (when comparing with the same version running on
JDK 32bit). Also IntelliJ IDEA 10.5.2 contains important bug fix for
complete indices flushing upon idle time of 5 seconds.

On 9/20/2011 10:50 PM, Stephen Boesch wrote:

Hi,
   I have been using IJ for three years and there is a distinct pattern: (a) IJ is great for smaller codebases.   (b) IJ falls flat with large codebases.

>

I have been trying to use IJ 9.x and 10.X at two internet companies having among the largest codebases in the world.  Eclipse is definitely doing a better job here.  At both companies I ended up relegating IJ to a secondary role since it could not deal with the codebases .

>

Here are some symptoms:

>

  • indexing taking forever. Sometimes completing in tens of minutes, other times have to kill after hour/(s)

>

  • index getting corrupted most times that IJ is shutdown and restarted

  • No option to turn off indexing (yes sometimes I want that..)

  • "Excluded directories" configured in the Project Module Settings dialog not "sticking" -- so IJ ends up indexing areas that I don't want.

>
>

These are just some of the issues.

>
>

Basically I want to ask the Jetbrains folks:  it's great to go and support a lot of new languages, sure.. but please put more focus on supporting large codebases.

>

---
Original message URL: http://devnet.jetbrains.net/message/5319966#5319966


0
Comment actions Permalink

Compared to most codebases, yes.  Compared to the ones I have been working on, no.

0
Comment actions Permalink

Glad to hear about the improvements coming along for IJ11 - especially for indexing!

I'm not trying to bash IJ here.  It's just the reality that it has been difficult to use in the largest environments. As long as there is a continued focus on makinig it more performant - and yes - the indexing is a key item here - then I have hope to  be looking forward to being able to continue to use IJ.

sincerely

stephenb

0
Comment actions Permalink

IJ11 has started to be rolled out for the developes at the (one of world's largest) codebases I work on.  We have been seeing improvements in the areas of indexing and overall performance.  This is good news - and  I have been  able to stick with IJ instead of Eclipse.  Thanks for the efforts.

0

Please sign in to leave a comment.