On 5 April 2015 at 08:35, Peter Hessler <phess...@theapt.org> wrote:
> I do the 32bit sparc packages builds.
>
> We hvae a cluster of 5 machines, and they take roughly 3 weeks to build
> if there are no crashes or other issues. Right now thought, not all
> machines are able to build, so it will be closer to 5 weeks.


On 5 April 2015 at 09:58, Landry Breuil <lan...@rhaalovely.net> wrote:
> Pending hardware & kernel reliability.. have some numbers:
> macppc: 3 hosts (Xserve G4, 2 MP running SP), around 15 days for ~8400 pkgs
> alpha: 2 hosts (DS20L MP running SP + DS10L), around 18/20 days for ~6900 pkgs
> sparc64: 3 SP hosts (2 v210 +, 1 v215), around 17 days for ~8300 pkgs
> hppa: 2 MP hosts (J6000 + J6700), around 9/10 days for ~6700 pkgs

Thanks for posting those figures.
Do you guys make any changes to the system configuration?
In this scenario, the user the build was running under was made a
member of the staff login class, home directory was mounted with
softdep & kern.bufcachepercent increased to 50.
pkgsrc has the ability to do unprivileged builds where the target is
the users home directory & the host operating system remains
untouched. There are facilities for doing distributing the workload
across multiple hosts or parallelising on a single host but 1) I've
not got my head around this process at all 2) lack of nullfs support
meant lots of duplication 3) didn't want to resort to using NFS as
this would need privileges to configure / mount.

The most painful part in pkgsrc can be the initial scan stage which
the entire contents of the pkgsrc directory is crawled to generate a
list of whats there & what dependencies there are, as this was running
as a single process, it took a long time, it did not help that a bad
commit after the tree was unlocked caused the build to fail, the other
item which we lost a day one was a build which had hung and as there
was no restriction on CPU time, the build was held up, the process was
killed & ulimit -t 7200 added to the config.

The bulkbuild on amd64 came to an end a few hours ago, the bulkbuild
on sparc64 is still in progress, the scan stage is extremely painful
there.
http://mail-index.netbsd.org/pkgsrc-bulk/2015/04/06/msg011484.html
The full report contains the logs generated at each stage of a failed
package (inside the link above).

Thanks to Ian for providing access to his machine.


Sevan / Venture37

Reply via email to