[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: build.sh: set creation is serialized
On May 1, 2008, at 4:26 PM, Manuel Bouyer wrote:
On Thu, May 01, 2008 at 04:14:09PM -0500, James Chacon wrote:
The issue, as I see it, is that the other parallel tasks during the
build are mostly CPU-bound, while this one may very well be I/O
depending on the hardware. You don't want to use only one core of
laptop for builds, just because its disk can't handle the last
done in parallel.
running the compiler, and building the binary sets have completely
workloads, so I think the parallelism for each should be configured
One can always run build.sh in different stages if thats truly an
but it's much easier to run a single command that does all the
issue for an individual system.
I'm not sure those systems are really "individual".
Sure...This is no different than if someone was building with any
other slow medium for disk. Should we slow down all parts of the build
which might not scale to everyone's hardware?
Remember, using -j was a conscious choice. If it doesn't scale for
your hardware, don't use it.
Basically, the knobs already exist but were disabled for everyone...
and I don't feel reenably it unconditiolany is right either.
As build.sh can run the different stages, couldn't it use 2 different
options for the parallelism of the different tasks ?
If there's reasonable patches, write some up. But otherwise I don't
see why people with sufficient hardware (i.e. basically any modern non-
laptop disks) should have to wait longer here. This impacts autobuild
just as well which is also annoying since the faster that can run, the
Main Index |
Thread Index |