There's no support for this at the moment. Long term it'll be tied to the
--parallel option, in particular with --parallel-threads but right now this
is not the case.

Whenever a task can be parallelized with create as many threads as there
are cores. We should change this, but it'll have to be with a -P option
since Gradle doesn't allow you to add new command line options (yet).

So you'll need to call it with:
./gradlew -PtaskThreads=2

Would that work for you? (We'll update Studio to have the same option).



On Fri, Feb 14, 2014 at 12:26 PM, Streets Of Boston <[email protected]
> wrote:

> Just bumping this question a little bit. Hope you all can forgive me :)
>
>
> On Wednesday, February 5, 2014 11:27:33 PM UTC-5, Streets Of Boston wrote:
>>
>> I have a quad core intel laptop, with 8GB ram and a 16GB swap file.
>> Only 4 to 5 GB are in use when it's building. It seems to be a pure
>> function of all 4 cores being used 100% by the java.exe processes used by
>> the build.
>>
>>
>> On Wednesday, February 5, 2014 4:40:53 PM UTC-5, sbarta wrote:
>>>
>>> Is your problem CPU or RAM? Those sorts of symptoms sound like a machine
>>> that's hitting swap really heavily, and in that case, setting CPU affinity
>>> isn't going to help a lot.
>>>
>>>
>>> On Wed, Feb 5, 2014 at 7:43 AM, Streets Of Boston 
>>> <[email protected]>wrote:
>>>
>>>> My 64 bit Windows 7 machine has 4 cores.
>>>>
>>>> When Android Studio builds, the java.exe processes that are spawned
>>>> take up all the CPU power of all the cores.
>>>> This slows down the rest of my laptop, where the mouse stutters,
>>>> keyboard gets unresponsive and other things slow down too much as well.
>>>>
>>>> Is there a way to limit these java.exe processes, i.e. the builds, to
>>>> certain core, i.e. set the affinity and do this permanently (not using the
>>>> task manager, because that works only as long as the java.exe process is
>>>> alive)?
>>>>
>>>> I tried TaskAssign.exe, but that doesn't seem to work for the java.exe
>>>> processes spawned by the build.
>>>>
>>>> I tried TaskAssign.exe to limit studio64.exe. This limits the IDE
>>>> itself to a limited number of cores and the java.exe spawned by
>>>> studio64.exe. But still, the java.exe processes spawned by the builds are
>>>> not limited.
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "adt-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>  --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to