search

strikersix23 / walkaround

Automatically exported from code.google.com/p/walkaround
Apache License 2.0
0 stars 0 forks source link

localWorkers=8 is excessive for some builders #105

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When ./deploy'ing walkaround by far the most resource-intensive step when the 
permutations are built.  On my work machine I was able to get past this step by 
assigning 4 GB of RAM to the VM process, on my home machine I just don't have 
enough physical ram to get past the OOMs.  I was able to easily compile the 
permutations by changing the localWorker count from 8 to 2.

I do recognize that reducing the worker count does increase compile time for 
those that have the resources available (although the permutations don't 
normally take that long to compile in any "healthy" environment to matter that 
much in my opinion), however I also recognize that there is no one correct 
number for every machine that is guaranteed to compile without either thrashing 
or "leaving power on the table" (although "make -j" using #CPU as a localWorker 
count seems like a good first step).

As this is likely to hit the "casual installer" the hardest I request that a 
blurb at least be put on RunningTheCode so that people recognize what is 
happening when their system starts melting down and understands what to do to 
fix it.  Of the half dozen files in the walkaround folder "build.xml" isn't one 
I thought I would need to edit to get this to work.

Original issue reported on code.google.com by eri...@teamworkgroup.com on 1 May 2012 at 1:52

GoogleCodeExporter commented 8 years ago 
Fixed in 
http://code.google.com/p/walkaround/source/detail?r=6c53fe4c72bb5ad69ff2efe5f73d
33d6e5a2258e .

Original comment by oh...@google.com on 9 May 2012 at 12:39