speed up port compiling using RAM (tmpfs) ???

Kris Kennaway kris at obsecurity.org
Fri Jan 20 15:41:56 PST 2006


On Fri, Jan 20, 2006 at 03:28:08PM -0800, Gayn Winters wrote:
> > [mailto:owner-freebsd-hackers at freebsd.org] On Behalf Of Kris Kennaway
> > Sent: Friday, January 20, 2006 11:47 AM
> > To: Gary Thorpe
> > Cc: Wesley Shields; Ashok Shrestha; Brandon Flowers; Kris 
> > Kennaway; Mike Meyer; freebsd-hackers at freebsd.org; Dag-Erling Sm?rgrav
> > Subject: Re: speed up port compiling using RAM (tmpfs) ???
> > 
> > 
> > On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote:
> > 
> > > >-j is not safe to use with port builds since many ported software
> > > >contain race conditions in the build.
> > > >
> > > >Kris
> > > 
> > > This effectively means that you cannot take advantage of SMP to
> compile 
> > > FreeBSD's ports collection. That sounds like a big 
> > > limitation...especially for people trying to speed up bulk builds.
> > 
> > Yeah, but what do you propose to do about it?  We have 14000 ports
> > that need to be inspected for build race conditions and fixed before
> > you can turn on -j by default.
> > 
> > Kris
> 
> 
> With a dual processor (even dual core?) is there a way to assign the big
> make to one processor and to assign the foreground activity (email,
> edits, etc) to another?  Is SMP somehow smart enough to do this
> automagically?

Yes, this is what will happen, more or less.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060120/ae138257/attachment.bin


More information about the freebsd-hackers mailing list