Date: Thu, 02 Jun 2005 12:34:23 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Maxim.Sobolev@portaone.com Cc: cvs-src@FreeBSD.org, Scott Long <scottl@samsco.org>, Tim Kientzle <kientzle@FreeBSD.org>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/lib/libarchive archive_private.h archive_read.c archive_read_data_into_fd.c archive_write.c archive_write_set_compression_bzip2.c archive_write_set_compression_gzip.c archive_write_set_compression_none.c Message-ID: <867jhdnj2o.fsf@xps.des.no> In-Reply-To: <429DF9E9.9060307@portaone.com> References: <200506011552.j51FqdR2046893@repoman.freebsd.org> <429DED77.9050003@samsco.org> <429DF37B.8010203@portaone.com> <429DF38B.2020107@samsco.org> <429DF9E9.9060307@portaone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev <sobomax@portaone.com> writes: > Therefore, IMHO, the only realistical approach is to improve > tinderboxes to minimize detection window (i.e. faster, multi-CPU > hardware and/or tools like ccache) and to make breakage information > delivery more direct. Faster, multi-CPU hardware will not help. The tinderbox is constrained by memory bandwidth, not CPU speed. A cluster of seven $200 Mini-ITX boxes can do a full -CURRENT tinderbox run in two or three hours, vs. eight to ten hours on a single $1400 box. Ccache won't help either, because buildworld always starts by building a new toolchain, which invalidates the cache. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867jhdnj2o.fsf>