perform builds on a different drive
Ion-Mihai Tetcu
itetcu at FreeBSD.org
Thu Sep 9 17:22:02 EDT 2010
On Thu, 09 Sep 2010 22:08:50 +0200
olli hauer <ohauer at gmx.de> wrote:
> On 2010-09-09 16:02, Dominic Fandrey wrote:
> > I intend to perform builds on a different drive similar to
> > setting WRKDIRPREFIX on a regular system. I have a drive I want
> > to dedicate to the task and which is mounted async, this is why
> > I don't want the more permanent files stored there.
> >
> > On this list I found the suggestion to just make ${tb}/<BUILD>
> > a symlink. However whenever I start a new build the symlink is
> > removed and the directory recreated.
> >
> > Is there any /working/ way to perform the builds somewhere else?
> >
> > Regards
> >
>
> If you have enough RAM try the following (my actual layout)
>
> drive 1:
> /usr/ports
> /data/distfiles
>
> drive 2:
> /tinderbox
> /jails
> /8.1 => md10 (200MB swap)
> /8.1.bin => copy of relX will be copied back to relX in
> ramdisk /8.1-FreeBSD => md11 (1400MB swap), buildspace_relX
>
>
> With this layout and the help of the ramdisks I need in duration
> ~50-60% the time for a build with my ~400 favorite ports.
> I build all my ports used in prod. regularly and it is quit a
> difference if the build needs 4 hours instead 8-10 hours without
> ramdisks.
>
> On my wish list is to mark a port build done if the port is build
> as decency for another port and have a higher queue id. I guess
> this can bring complete build time to 2 hours instead of 4.
>
> PS:
> In all my builds I never hit the 1400MB limit for md11.
A 2GB for the build md is usually safe. But the biggest port needs
about 10 times as much.
--
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20100910/e9796cbf/attachment.bin>
More information about the tinderbox-list
mailing list