JetGradle and java processes

Hello,

What I noticed recently is that on 'Refresh' JetGradle plugin creates 2 java processes that is pretty reasonable since it lauches gradle compilation on background. However when tasks are done both processes are kept in memory and consume around 300-400 MB both.

Is this intentional and serves faster subsequent refreshes or does it sound like a bug?

Thanks!

4 comments
Comment actions Permalink

Last time I noticed 2 processes consuming 800MB of memory. This is for approx. 14-16 subprojects. Quite large foorprint.

0
Comment actions Permalink

Hi Eduard,

That is a gradle-imposed limitation:

The Tooling API uses the daemon all the time, e.g. you cannot officially use the Tooling API without the daemon. This means that subsequent calls to the Tooling API, be it model building requests or task executing requests can be executed in the same long-living process.


Also note that there was a problem that caused multiple daemon processes creation - GRADLE-2228. Make sure you don't suffer from it.

Denis
0
Comment actions Permalink

Great, so with 1.1 and further there will be only 1 deamon. Thanks for pointing to gradle doc and reported ticket. Meanwhile I'll be killing them manually.

0
Comment actions Permalink

I believe a nightly gradle build already contains the fix.

Denis

0

Please sign in to leave a comment.