From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/109130
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Sylvain Hubert <champignoom@gmail.com>
Newsgroups: gmane.comp.tex.context
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Thu, 29 Oct 2020 15:14:49 +0100
Message-ID: <CACNy3ND-trxFLNKGwwAktyY2o9Q1pZjW=Ri7xqQ9yqhKOT0Qjg@mail.gmail.com>
References: <CACNy3NAD9nngav9wnFSiFG1FmAkEv-eXQ4Sk81n06mp56ayqYg@mail.gmail.com>
 <B2CB0189-F024-4E3A-A708-286D88FD4972@elvenkind.com>
 <CACNy3NAmt5Q2f5RZsdGnBHtuR5Mdr7ieLKjK7nQH=0ytvNHOpA@mail.gmail.com>
 <3940DC89-A350-4034-B34A-1BDE401C46D5@elvenkind.com>
 <CACNy3NC2_yo1GkMm1J5nscnRs4m5b51y2Fmt2Tjpw5TY4czDsw@mail.gmail.com>
 <8AB0A48D-9D67-4DCF-9F1C-30B8268C6D9E@elvenkind.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8105426988541276631=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="33644"; mail-complaints-to="usenet@ciao.gmane.io"
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Thu Oct 29 15:15:35 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1kY8iF-0008d7-Ay
	for gctc-ntg-context-518@m.gmane-mx.org; Thu, 29 Oct 2020 15:15:35 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id CAF711A9B87;
	Thu, 29 Oct 2020 15:15:05 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OuuJtblanPjA; Thu, 29 Oct 2020 15:15:04 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id EA49C1A9BA0;
	Thu, 29 Oct 2020 15:15:04 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 45F451A9B8A
 for <ntg-context@ntg.nl>; Thu, 29 Oct 2020 15:15:03 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id gWyAb9g1ym_h for <ntg-context@ntg.nl>;
 Thu, 29 Oct 2020 15:15:02 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.166.49;
 helo=mail-io1-f49.google.com; envelope-from=champignoom@gmail.com;
 receiver=<UNKNOWN> 
Original-Received: from mail-io1-f49.google.com (mail-io1-f49.google.com
 [209.85.166.49])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 495AF1A9B87
 for <ntg-context@ntg.nl>; Thu, 29 Oct 2020 15:15:02 +0100 (CET)
Original-Received: by mail-io1-f49.google.com with SMTP id b15so3534262iod.13
 for <ntg-context@ntg.nl>; Thu, 29 Oct 2020 07:15:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=4p87RzXGZOXgmVLWteIrkpoFrFmG5x6yAAwfT+K4+nw=;
 b=PMF9qJmayY+4buiv2jUyob6ACAcgi+iN9EWOcauFVB8sI/BsPxpJ8+/C1JcAE67Uf+
 7e8c6b/9xrERl672PcMqzVfsLfFZ9V9M0eAWO4Tz3/EAYjc5PxPQbPTmJ3vkpEPU8ped
 QkGfRqzRtrXhC0fVtbVbNrU0fXFKXt+KdM+hk2Ndzw29wIJzMIlYeJ1GEMv72z15dyx+
 a5EbtjGLEQSRgC9VMKJmNe7gKmhntp6iQrPNgGv5uoxrzpk9ghxVVGtNTDpGGqVsq0QT
 dtkyI3g4yYlV9oGqbTaPRwsvcHWI+cRrSBZK0D1hBXDpwGv692/H0IA9l1577BwM/4hc
 qZ1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=4p87RzXGZOXgmVLWteIrkpoFrFmG5x6yAAwfT+K4+nw=;
 b=Vr4qVZozqJyBxB4YYKxNOdiyOfi+pPikM94GY5gvIe5gCh3LOl/grH09pVfsqXHqAZ
 05iE7XLkaIWfv4y6+zs+PPCEAIQvo5TQbZpgWFKU2mkcrQ0INfVW9fzho/YHAgjjYzIW
 /apLVC8hFta0ELz6m5duRGWtIwRNZALOldV6dqVMqckkot9Vqsg6Hz/xYlqssf1JJnFr
 8f4O3m0Qj7cB1zueAR6JXOaMt4CK8X+5pt3RDjaK5sbV+Ksp8TX0GDx461x59GgKdUu1
 Nup8TNpFH9uApddeH0JbRgvZlLCa2/XeFGF5SvZ5nvgLvM4wVRQkvUxppBhASS2rhPyZ
 nsSQ==
X-Gm-Message-State: AOAM531AmIB6ANKDFJUmWhQAtGwL4/73/DI7vwmc78CMlgICqV72NAPq
 Y3TK9OzIA4yJSXnsvLWh9pJcZ14JHMu4MdlaFggiYgakQ5/2FQ==
X-Google-Smtp-Source: ABdhPJxfm/pd9EPTgBKMLUw/xYX7DPD04Ev6sNgFX5FJiOhVFSg+TR3HWRIyE42yeXB2UhAtfDdmgn82/wQKElt7Ans=
X-Received: by 2002:a02:3f59:: with SMTP id c25mr3770219jaf.17.1603980900407; 
 Thu, 29 Oct 2020 07:15:00 -0700 (PDT)
In-Reply-To: <8AB0A48D-9D67-4DCF-9F1C-30B8268C6D9E@elvenkind.com>
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:109130
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/109130>

--===============8105426988541276631==
Content-Type: multipart/alternative; boundary="000000000000cb9c9b05b2cfe7fc"

--000000000000cb9c9b05b2cfe7fc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> But it seems to be a big problem only on your machine
I fail to see what this implies.

> What hardware are you running on? Is it a Raspberry PI?
No, it's Core i5 + 8G ram + ssd.

> Like any TeX-related program, ConTeXt does a fair bit of disk access
while starting up.
But none of the other TeX-related programs causes such a problem here.

> And it certainly should not have an effect on the CPU usage of any other
program.
Indeed it should not have such an effect, so it failed to avoid what I
should have avoided, and that's why it's a bug to be discovered and
eliminated.

On Thu, 29 Oct 2020 at 13:56, Taco Hoekwater <taco@elvenkind.com> wrote:

>
>
> > On 29 Oct 2020, at 12:44, Sylvain Hubert <champignoom@gmail.com> wrote:
> >
> > I've just tried chromium which behaves a bit better but still
> experiences a sudden raise of cpu usage from <10% to >70% during ~1s.
> > I've also noticed that, even without any browser running, each time
> after I compile a file with `context`, my terminal get stuck for ~1s.
> > So I'm pretty sure this is a context bug, probably caused by unnecessar=
y
> excessive disk operations or something.
>
> But it seems to be a big problem only on your machine. What hardware are
> you running on? Is it a Raspberry PI?
>
> Like any TeX-related program, ConTeXt does a fair bit of disk access whil=
e
> starting up, but I haven=E2=80=99t heard of that being an actual problem =
since the
> age of single-core CPUs. And it certainly should not have an effect on th=
e
> CPU usage of any other program (it could affect system responsiveness,
> though).
>
> Best wishes,
> Taco
>
>
>
>
>
> _________________________________________________________________________=
__________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
>
> _________________________________________________________________________=
__________
>

--000000000000cb9c9b05b2cfe7fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>&gt; But it seems to be a big problem only on your ma=
chine</div><div>I fail to see what this implies.<br></div><br><div>&gt; Wha=
t hardware are you running on? Is it a Raspberry PI?</div><div>No, it&#39;s=
 Core i5 + 8G ram + ssd.</div><div><br></div><div>&gt; Like any TeX-related=
 program, ConTeXt does a fair bit of disk access while starting up.</div><d=
iv>But none of the other TeX-related programs causes such a problem here.<b=
r> </div><div><br></div><div>&gt; And it certainly should not have an effec=
t on the CPU usage of any other
 program.</div><div>Indeed it should not have such an effect, so it failed =
to avoid what I should have avoided, and that&#39;s why it&#39;s a bug to b=
e discovered and eliminated.<br></div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, 29 Oct 2020 at 13:56, Taco Ho=
ekwater &lt;<a href=3D"mailto:taco@elvenkind.com">taco@elvenkind.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
&gt; On 29 Oct 2020, at 12:44, Sylvain Hubert &lt;<a href=3D"mailto:champig=
noom@gmail.com" target=3D"_blank">champignoom@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; I&#39;ve just tried chromium which behaves a bit better but still expe=
riences a sudden raise of cpu usage from &lt;10% to &gt;70% during ~1s.<br>
&gt; I&#39;ve also noticed that, even without any browser running, each tim=
e after I compile a file with `context`, my terminal get stuck for ~1s.<br>
&gt; So I&#39;m pretty sure this is a context bug, probably caused by unnec=
essary excessive disk operations or something.<br>
<br>
But it seems to be a big problem only on your machine. What hardware are yo=
u running on? Is it a Raspberry PI?<br>
<br>
Like any TeX-related program, ConTeXt does a fair bit of disk access while =
starting up, but I haven=E2=80=99t heard of that being an actual problem si=
nce the age of single-core CPUs. And it certainly should not have an effect=
 on the CPU usage of any other program (it could affect system responsivene=
ss, though).<br>
<br>
Best wishes,<br>
Taco<br>
<br>
<br>
<br>
<br>
___________________________________________________________________________=
________<br>
If your question is of interest to others as well, please add an entry to t=
he Wiki!<br>
<br>
maillist : <a href=3D"mailto:ntg-context@ntg.nl" target=3D"_blank">ntg-cont=
ext@ntg.nl</a> / <a href=3D"http://www.ntg.nl/mailman/listinfo/ntg-context"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ntg.nl/mailman/listinfo/nt=
g-context</a><br>
webpage=C2=A0 : <a href=3D"http://www.pragma-ade.nl" rel=3D"noreferrer" tar=
get=3D"_blank">http://www.pragma-ade.nl</a> / <a href=3D"http://context.aan=
het.net" rel=3D"noreferrer" target=3D"_blank">http://context.aanhet.net</a>=
<br>
archive=C2=A0 : <a href=3D"https://bitbucket.org/phg/context-mirror/commits=
/" rel=3D"noreferrer" target=3D"_blank">https://bitbucket.org/phg/context-m=
irror/commits/</a><br>
wiki=C2=A0 =C2=A0 =C2=A0: <a href=3D"http://contextgarden.net" rel=3D"noref=
errer" target=3D"_blank">http://contextgarden.net</a><br>
___________________________________________________________________________=
________<br>
</blockquote></div>

--000000000000cb9c9b05b2cfe7fc--

--===============8105426988541276631==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============8105426988541276631==--