From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51314)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gCAQB-0004FS-Pn
	for guix-patches@gnu.org; Mon, 15 Oct 2018 17:29:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gCAQA-0003RE-Vk
	for guix-patches@gnu.org; Mon, 15 Oct 2018 17:29:03 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:47289)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gCAQA-0003Qq-O3
	for guix-patches@gnu.org; Mon, 15 Oct 2018 17:29:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gCAQA-00059G-Ly
	for guix-patches@gnu.org; Mon, 15 Oct 2018 17:29:02 -0400
Subject: bug#32980: [PATCH 0/2] Multiplexed build output from the daemon
Resent-To: guix-patches@gnu.org
Resent-Message-ID: <handler.32980.D32980.153963888419704.done@debbugs.gnu.org>
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
References: <20181007222945.2077-1-ludo@gnu.org>
Date: Mon, 15 Oct 2018 23:27:55 +0200
In-Reply-To: <20181007222945.2077-1-ludo@gnu.org> ("Ludovic
	\=\?utf-8\?Q\?Cour\?\= \=\?utf-8\?Q\?t\=C3\=A8s\=22's\?\= message
	of "Mon, 8 Oct 2018 00:29:45 +0200")
Message-ID: <87tvlmc338.fsf@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: 32980-done@debbugs.gnu.org

Hello,

Ludovic Court=C3=A8s <ludo@gnu.org> skribis:

> The downside of the protocol is that it creates quite some overhead.  For
> example, when extracting a tarball, we see things like:
>
>   read(13, "gmlo\0\0\0\0", 8)             =3D 8
>   read(13, "5\0\0\0\0\0\0\0", 8)          =3D 8
>   read(13, "@ build-output 25935 29\ncoreutils-8.29/m4/fseterr.m4\n", 53)=
 =3D 53
>   read(13, "\0\0\0", 3)                   =3D 3
>
> That is, a 29-byte message with a 24-byte header (plus the
> 8 + 8 + 3 =3D 19 bytes of the underlying protocol; see =E2=80=98process-s=
tderr=E2=80=99.)

I timed =E2=80=9Cguix build -S binutils --check=E2=80=9D, which includes th=
e output of
=E2=80=9Ctar xvf=E2=80=9D followed by =E2=80=9Ctar cvf=E2=80=9D, and the ti=
ming difference is not
noticeable (of course the peak of CPU activity is caused by xz.)

Anyway I went ahead and pushed this as
f9a8fce10f2d99efec7cb1dd0f6c5f0df9d1b2df.

I changed =E2=80=9C@ build-output=E2=80=9D to =E2=80=9C@ build-log=E2=80=9D=
, and also adjusted
tests/status.scm since new tests had been added to that file in the
meantime.

Ludo=E2=80=99.