On Jan 8, 2011, at 3:10 PM, Erik Cederstrand wrote: > Hello Pav, > > Den 08/01/2011 kl. 20.34 skrev Pav Lucistnik: > >> Package cluster is quite clever, akshully, and since this is OT here, >> just terse comments > > Sorry, replied to a bad message... redirecting to current_at_ > >>>> 1. adding SSD disks >> >> irrelevant because of bullet 2. >> >>>> 2. source and destination directories on md devices >> >> already done, swap backed md devices are used >> >>>> 3. huge ccache cache >>>> 4. dist-cc >> >> these tend to have their own issues >> >>>> 5. some heuristics on which ports could be skipped because dependencies haven't changed since last run >> >> this is also already done, we call it "incremental builds" >> >>>> 6. tuning the host system for this specific task >> >> empty words > > I was pretty sure I couldn't improve anything with 5 minutes of thinking. I'm glad the most obvious things have already been done, and I'm sure you and others have put a lot of effort into this. My question was more what, if anything, can be done to speed up the cluster. > > Also, how long does it take to complete an exp-run on the cluster? Erik, As I said before, the tinderbox / exp-run infrastructure needs to be made portable, the infrastructure needs to be there, and as extra credit (I've stated this in other emails in the past) parallelization in ports/pkg_install needs to be fixed as ports/packaging in FreeBSD doesn't work in an ACID[1]-like manner. I'd rather not repeat the reasons in greater detail. Please look for my replies to this thread on current_at_ for more details in "part A", and look for my replies on ports_at_ for more details in "part B". Thanks, -Garrett 1. http://en.wikipedia.org/wiki/ACIDReceived on Sat Jan 08 2011 - 22:56:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:10 UTC