From mboxrd@z Thu Jan 1 00:00:00 1970 From: taylanbayirli@gmail.com (Taylan Ulrich =?utf-8?Q?Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer?=) Subject: Re: [PATCH] build: pull: Compile .scm files in one process. Date: Fri, 06 Nov 2015 17:41:31 +0100 Message-ID: <87d1vnxepw.fsf@T420.taylan> References: <87si4kxtge.fsf@T420.taylan> <87611frtsx.fsf@igalia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zuk53-0002mA-Rw for guix-devel@gnu.org; Fri, 06 Nov 2015 11:41:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zuk50-000518-2b for guix-devel@gnu.org; Fri, 06 Nov 2015 11:41:37 -0500 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:33998) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zuk4z-0004zm-ST for guix-devel@gnu.org; Fri, 06 Nov 2015 11:41:34 -0500 Received: by wmnn186 with SMTP id n186so46806516wmn.1 for ; Fri, 06 Nov 2015 08:41:33 -0800 (PST) In-Reply-To: <87611frtsx.fsf@igalia.com> (Andy Wingo's message of "Fri, 06 Nov 2015 16:12:14 +0000") 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: Andy Wingo Cc: guix-devel@gnu.org Andy Wingo writes: > On Thu 05 Nov 2015 17:10, taylanbayirli@gmail.com (Taylan Ulrich "Bay=C4= =B1rl=C4=B1/Kammer") writes: > >> CPU: >> >> It used to max out every CPU core, now just one. :-) >> >> >> Time: >> >> It used to take ~18 minutes on my machine, now less than 3. > > If you compile within a par-for-each you should be able to peg your CPU > core again, but actually reduce the time :) >From what I understand, that would probably ignite the bug again. We need to ensure that as soon as a module file is compiled, it's also explicitly loaded before anything else is compiled (which might import it), otherwise that compilation will import the "degenerate" version of the module that results from compiling but not loading it. But that's really just my shallow high-level understanding of the bug, and could be way off. If you have any insights on what's really going on, that would be greatly appreciated. :-) Taylan