atom feed40 messages in org.freebsd.freebsd-archRe: Removing wait union
FromSent OnAttachments
Mike BarcroftJun 1, 2002 10:00 pm.diff, .diff
Bruce EvansJun 2, 2002 8:21 am 
Mike BarcroftJun 3, 2002 4:07 pm 
Kris KennawayJun 3, 2002 4:24 pm 
Terry LambertJun 3, 2002 4:49 pm 
Garance A DrosihnJun 3, 2002 5:51 pm 
Kris KennawayJun 3, 2002 6:15 pm 
Terry LambertJun 3, 2002 6:24 pm 
Terry LambertJun 3, 2002 6:33 pm 
Kris KennawayJun 3, 2002 6:37 pm 
Kris KennawayJun 3, 2002 6:38 pm 
John BaldwinJun 3, 2002 6:42 pm 
Will AndrewsJun 3, 2002 8:42 pm 
Terry LambertJun 3, 2002 11:22 pm 
Terry LambertJun 3, 2002 11:42 pm 
Terry LambertJun 3, 2002 11:44 pm 
Bakul ShahJun 4, 2002 10:52 am 
Garance A DrosihnJun 4, 2002 11:34 am 
Kris KennawayJun 4, 2002 2:09 pm 
Brian SomersJun 4, 2002 2:20 pm 
Garrett WollmanJun 4, 2002 2:30 pm 
Poul-Henning KampJun 4, 2002 2:55 pm 
Mike BarcroftJun 4, 2002 4:07 pm 
Terry LambertJun 4, 2002 4:08 pm 
Terry LambertJun 4, 2002 4:10 pm 
Mike BarcroftJun 4, 2002 4:18 pm 
Garance A DrosihnJun 4, 2002 4:26 pm 
Kris KennawayJun 4, 2002 4:30 pm 
Terry LambertJun 4, 2002 4:30 pm 
Terry LambertJun 4, 2002 4:49 pm 
Bakul ShahJun 4, 2002 5:50 pm 
Mike BarcroftJun 4, 2002 7:11 pm 
Terry LambertJun 4, 2002 7:49 pm 
Garance A DrosihnJun 4, 2002 7:50 pm 
Steve KarglJun 4, 2002 7:57 pm 
Alfred PerlsteinJun 4, 2002 8:15 pm 
Terry LambertJun 4, 2002 9:06 pm 
Brian SomersJun 5, 2002 11:24 am 
Garance A DrosihnJun 5, 2002 2:37 pm 
David O'BrienJun 6, 2002 10:16 am 
Subject:Re: Removing wait union
From:Kris Kennaway (kr@obsecurity.org)
Date:Jun 3, 2002 6:37:05 pm
List:org.freebsd.freebsd-arch

On Mon, Jun 03, 2002 at 06:24:45PM -0700, Terry Lambert wrote:

No, you don't need a cluster.

Um, yes you do.

I think people are not understanding the problem.

The problem is that a change to the system breaks the build of a package.

What this means is that you should be able to:

1) Build all the packages on a system 2) Install everything that wasn't automatically installed as a dependency

Um, Terry, we have over 7000 ports now. It takes our 8-way cluster 20 hours to build them (sorry, the 8 hours I said earlier was wrong); as already stated it runs at close to 100% capacity the entire time. Therefore a good estimate of the number of equivalent CPU-hours is 8*20 hours = 6 2/3 CPU-days.

Very little time is wasted with the cluster sitting idle waiting for dependencies to build (and I can probably get that down to 0 time wasted if I just reorder the makefile a bit to start the build of long dependency branches like GNOME first - GNOME and KDE are the only "choke points" where the cluster ends up idling for a few minutes except for one or two machines: by that time everything else is finished anyway).

Two very different problems. The solution of the first needs a ports cluster to be able to solve it within about 8 hours. But the much of that 8 hours is based on dependency ordering that you can throw away, if you are trying to solve the "system changed" problem, rather than the "ports changed" problem.

Make sense?

No, because the above is wrong ;-)

Please accept that I actually know what I'm talking about (since I've been managing the ports cluster for about 8 months now) and just drop the matter.

Kris