Date: Mon, 15 May 2006 14:39:39 +0100 From: Ashley Moran <work@ashleymoran.me.uk> To: freebsd-questions@freebsd.org Cc: Bill Moran <wmoran@collaborativefusion.com>, Richard Collyer <richard@firebadger.net> Subject: Re: Please explain make -j to my little brain Message-ID: <200605151439.39957.work@ashleymoran.me.uk> In-Reply-To: <4468569B.6060706@firebadger.net> References: <200605151112.33416.work@ashleymoran.me.uk> <4468569B.6060706@firebadger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 15 May 2006 11:23, Richard Collyer wrote: > The way I understand it is that 1 core would do this... > > compile .... read disk .... compile .... read disk ... compile > > It wont be reading when it is compiling and cant compile when its > reading so if you do -j 2 even on a single core machine it could do: > > compile .... read disk .... complile .... read disk ... compile > read disk .... complile .... read disk ... compile .... read disk > > Which means neither the CPU or the disks are idle resulting in faster > performance. Thanks Richard + Bill I get it now. Presumably with faster disks, the lower the number of make processes you require. Ashley -- "If you do it the stupid way, you will have to do it again" - Gregory Chudnovsky
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605151439.39957.work>