Optimizing "make release"

Hi!

In an effort to run benchmarks on the latest CURRENT on a couple of slave machines, I need to build the distribution sets necessary for an NFS install as fast as possible (the slaves are installing over PXE), but still ending up with something as close as possible to a normal default installation on the slaves.

Right now, I'm doing a very basic run to create the distribution sets (using a default make.conf and a 6.2-STABLE build machine):

# /cd /usr/src
# csup /etc/current-supfile
# make buildworld
# cd /release
# make release BUILDNAME=CURRENT-YYYYMMDDHHMMSS CVSROOT=/home/ncvs CHROOTDIR=/home/chroot

Using the above commands, a lot of stuff gets compiled unnecessarily, and the process takes 5-6 hours on a 2GHz P4. I'd like to cut that to 2 hours max. I tried to use some of the NO_* settings in make.conf, but it's not clear to me what I can omit. Some things are needed later in make release (e.g. NO_CXX) even though I don't need a C++ compiler on the slave systems. I also looked a ccache, but I consider it somewhat dangerous, since I need to have an absolutely correct, reproducible installation rather than a fast build.

If I ignore documentation distfiles (will this affect benchmarks in any way?), AFAICT the only distribution sets I need are base, proflibs, kernels and (maybe) lib32. Is there a way to get "make release" to do just that? I'm open to other suggestions, of course.

Thanks,
Erik
_______________________________________________
freebsd-performance@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Optimizing "make release"
    ... In an effort to run benchmarks on the latest CURRENT on a couple of slave ... machines, I need to build the distribution sets necessary for an NFS install ... I'm doing a very basic run to create the distribution sets (using ... reproducible installation rather than a fast ...
    (freebsd-performance)
  • Re: FIXMBR redux
    ... Michael Solomon wrote: ... > you change the slave to the master, the former slave drive has a cloned ... > image from a different hard drive of an OS installation that was installed ... you to help me restore my original master OS to the ...
    (microsoft.public.windowsxp.basics)
  • Re: Need to access slave XP drive to remove console password
    ... installation therefore sys knows nothing about the slave win installation - ... If you try and repair the win on the slave you would, I think, finish up ... with a dual boot of win, and the boot record would be still on C, thus if ... the recovery console announces that the recovery ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Old windows hard disk as slave
    ... connected the drive as slave after I had installed XP on the new file I could not boot up and got the message "Error opening operating system" so assumed it was the old registry/windows on the slave drive. ... This was the original problem with the old installation as the computer refused to boot with the above message. ...
    (uk.comp.homebuilt)
  • Re: Adding old hard drive to new computer
    ... added didn't have a jumper so I left it that way, after installation all ... your present system will just see it as a slave containing data.. ... > Mike Hall ... > MVP - Windows Shell/User ...
    (microsoft.public.windowsxp.hardware)