We have been migrating to use Gradle for all our builds.
We have three library projects that are loaded separately. Two of them have a relatively small number of projects, and load very quickly.
The third one is pretty large, with near to 70 subprojects (all of which are generally pretty small).
This large project has grown to the point where doing a refresh from IntelliJ IDEA (14.1.4) is extremely painful.
It used to take an annoying, but relatively short time when a change was made to the root project. It could take 30-45 seconds.
It has grown however, to take upwards of 20 minutes to do a refresh when I manually hit the refresh button, or a change to the root project occurs.
Are there any ways I should go about troubleshooting this? It just seems to slow down, and takes longer and longer under tasks "Gradle: Resolve dependencies ':xyz'".
I can run a full command line build with the gradle wrapper (v2.5), very quickly, so it is not that we have gone beyond some limit with Gradle itself.
Looking at the task manager (on Windows), IntelliJ idea isn't using any significant CPU time, but is using over a gig of RAM. This amount is not especially concerning, unless it is bumping up to some limit that is causing things to go slow. Our development machines have more than enough RAM to run the task (my machine in this particular instance has 96 gig of RAM, so there is plenty to allocate if necessary).
Mark E. Scott, Jr.