From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Sylvain Hubert <champignoom@gmail.com>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Thu, 5 Nov 2020 12:25:58 +0100 [thread overview]
Message-ID: <61fae008-745b-4461-ea5b-ce399c75eb64@xs4all.nl> (raw)
In-Reply-To: <CACNy3NC=AbWk7z_d+FkjZ0oH4wOEWzcp8=Qo8849Bx76CFAcNw@mail.gmail.com>
On 11/5/2020 11:48 AM, Sylvain Hubert wrote:
> After dozens of compilations of various minimal examples using the newly
> installed context, the problem reappeared.
>
> Removing tex/texmf-cache does not help.
Removing firefoxe does ... when I open e.g. the cnn website in firefox
(for instance to keep an eye on crazy elections), that program takes 650
MB memory and 44% GPU while edge (or chrome) takes 270 MB mem and 3%
GPU. Add a few more tabs and firefox will easily eat up gigs of mem.
Now, I don't know how it manages memory but the tex engine needs a few
reasonable sized arrays but in large allocs and then it manages its own
memory from that pool, Lua needs more mem (could be scattered due to
allocs i guess), and soem garbage collection can kick in, and browsers
... well i suppose lots of allocations and it also depends on the
jasvascript vm.
So, I would not be surprised if after some runs of these programs you
end up with scattered memory. I suppose that at some point the operating
system (when in rest) will sort things out. When I make a format file it
normally takes a few seconds. When I let firefox run wild on memory (top
out mem and then let it give back some), it can take twice as much to
make a format, but after quitting firefox it's all ok again.
Anyway, already long ago I decided that firefox is a memory hog so
whenever I do something that takes more time than I susspect, I close
firefox. Actually I often close browsers when i don't need them, also
because they always seem to be busy with something (also the network).
Tex is just juggling some bytes. In the past tex and distributioen were
considered large ... nowadays they are small compared to whatever you
install and run. And in luametatex/context the performance bottleneck is
lua, not the core tex engine.
Of course you could consider swithcing to another operating system.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-05 11:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:29 Sylvain Hubert
2020-10-29 11:00 ` Taco Hoekwater
2020-10-29 11:15 ` Sylvain Hubert
2020-10-29 11:19 ` Sylvain Hubert
2020-10-29 11:31 ` Taco Hoekwater
2020-10-29 11:44 ` Sylvain Hubert
2020-10-29 12:55 ` Taco Hoekwater
2020-10-29 14:14 ` Sylvain Hubert
2020-10-29 15:38 ` Taco Hoekwater
2020-10-29 16:44 ` Sylvain Hubert
2020-10-29 17:15 ` Hans Hagen
2020-10-29 14:18 ` Sylvain Hubert
2020-10-29 15:04 ` Hans Hagen
2020-10-30 8:34 ` ntg
2020-10-30 9:06 ` Taco Hoekwater
2020-10-30 18:44 ` Sylvain Hubert
2020-10-30 19:14 ` Sylvain Hubert
2020-10-30 19:26 ` Hans Hagen
2020-10-30 18:48 ` Sylvain Hubert
2020-10-30 19:28 ` Hans Hagen
2020-10-29 11:26 ` Sylvain Hubert
2020-10-29 15:48 ` Aditya Mahajan
2020-10-29 16:56 ` Sylvain Hubert
2020-11-04 15:01 ` Sylvain Hubert
2020-11-05 10:48 ` Sylvain Hubert
2020-11-05 11:01 ` Taco Hoekwater
2020-11-05 11:49 ` Sylvain Hubert
2020-11-05 11:25 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61fae008-745b-4461-ea5b-ce399c75eb64@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=champignoom@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).