Now that the HP blades have been retired, tighten the requirements for
package build nodes.
This commit is contained in:
parent
8c92393ae5
commit
9d60518c46
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=37314
1 changed files with 12 additions and 8 deletions
|
@ -1327,6 +1327,13 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
|
||||||
<literal>portmgr</literal>.
|
<literal>portmgr</literal>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<note>
|
||||||
|
<para>Due to some generous donations, <literal>portmgr</literal> is
|
||||||
|
no longer looking for the loan of &i386; or <literal>amd64</literal>
|
||||||
|
systems. However, we are still interested in borrowing tier-2
|
||||||
|
systems.</para>
|
||||||
|
</note>
|
||||||
|
|
||||||
<sect2 id="node-requirements">
|
<sect2 id="node-requirements">
|
||||||
<title>Node requirements</title>
|
<title>Node requirements</title>
|
||||||
|
|
||||||
|
@ -1335,11 +1342,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>CPU capacity: TBA. However, we have several dual-CPU
|
<para>CPU capacity: anything less than 500MHz is generally
|
||||||
P-III &i386; 1.0GHz machines available, so anything with
|
not useful for package building.</para>
|
||||||
less horsepower than that is not as likely to be useful.
|
|
||||||
(However, many of our &sparc64;s are single-CPU, 500MHz
|
|
||||||
machines, so our requirements are lower.)</para>
|
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>We are able to adjust the number of jobs
|
<para>We are able to adjust the number of jobs
|
||||||
|
@ -1349,9 +1353,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>RAM: TBA. Again, we have been tuning to one job
|
<para>RAM: Less than 2G is not very useful; 8G or more
|
||||||
per 512M of RAM. (Anything less than 512M is very
|
is preferred. We have been tuning to one job
|
||||||
unlikely to be useful.)</para>
|
per 512M of RAM.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
Loading…
Reference in a new issue