From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Suggestion: disable offloading for texlive builds on hydra? Date: Sun, 26 Oct 2014 03:36:03 -0400 Message-ID: <87ppdf1dwc.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiIN5-0006Kv-Mm for guix-devel@gnu.org; Sun, 26 Oct 2014 03:36:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XiIMz-0007rS-Q8 for guix-devel@gnu.org; Sun, 26 Oct 2014 03:36:15 -0400 Received: from world.peace.net ([96.39.62.75]:48329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiIMz-0007rL-N2 for guix-devel@gnu.org; Sun, 26 Oct 2014 03:36:09 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org When texlive is built on hydra, the build slave that built it is tied up for 12 hours or more waiting for the build outputs (over 3 gigabytes!) to be transferred back to hydra. By design, only one transfer can happen at a time from a given build slave, so during those 12 hours, the build slave's CPU is left idle, and typically another 3 built-but-not-yet-transferred packages must wait until the texlive transfer finishes. I suggest that we arrange for hydra.gnu.org to build texlive locally for x86_64 and i686, to avoid this problem. What do you think? Mark