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

[Dag-Erling Smørgrav]

Maxim Sobolev <sobomax at 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
-- 
Dag-Erling Smørgrav - des at des.no