From: Hans Hagen <j.hagen@xs4all.nl>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX capacity exceeded
Date: Wed, 19 May 2021 19:22:12 +0200 [thread overview]
Message-ID: <6c2d023a-4451-df59-44a7-8fa2184abc40@xs4all.nl> (raw)
In-Reply-To: <6a4939bd-50ca-ef87-ca2a-1b517c4ff2e0@uni-bonn.de>
On 5/19/2021 6:49 PM, Thomas A. Schmitz wrote:
>
> On 19.05.21 18:34, Hans Hagen wrote:
>>>
>> Can you check the latest upload? You should be able to go way higher.
>
> Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
> trying your suggestions for improving the Lua code and rethinking my
> tables for analyzing the vocabulary. Thank you for the quick fix! And I
> hope there won't be any problem for other users - I'm aware that memory
If they have problems it's because of other changes -)
> on computers can differ vastly. I sometimes run ConTeXt on my raspberry
> pi 3, which has just 1 G of RAM, whereas my newish iMac at home has 40
> G. So it's difficult to find the sweet spot that will satisfy everybody...
Unless you use many huge fonts, running your document on a rpi 4 with
4-8 gb should work ok (we have a rpi 4 in mojcas compile farm connected
to an usb3 ssd). My laptop is from 2013 (decent intel 3840QM cpu + 16 GB
mem and ssd and so) and is about 3 times slower than the rpi 4 in the
luametatex manual.
Your file in mkiv does a decent ppm (is that an arm or intel mac?)
mkiv lua stats > lua properties: engine: lua 5.3, used memory: 601 MB,
ctx: 579 MB, max: unknown MB, hash chars: min(64,40), symbol mask: utf (τεχ)
mkiv lua stats > runtime: 22.310 seconds, 1068 processed pages, 1068
shipped pages, 47.871 pages/second
so I suppose in lmtx it's a bit faster and using less mem. Still less
mem than the GB's that e.g. firefox consumes after a few hours sitting
idle.
Concerning the sweetspot: I supose that on a laptop or desktop users are
okay, but in a vm (or instance) it might matter because there processes
have to fight over memory and cache (some is gained back by often faster
disk io because that gets delegated to another process). I try to keep
that in mind with luametatex/lmtx, which is why I spent quite some time
on a lower mem footprint. I have no clue what a modern cpu does compared
to mine (tex is single core).
(btw, the latest version should also be a bit more efficient / faster
with some huge cjk fonts that for some reasons have so many zero entries
that the tma file was 3 times larger than needed, but I suppose fonts
will always be a bit of an issue ... they have always been since tex
showed up.)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-05-19 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 21:43 Thomas A. Schmitz
2021-05-18 13:35 ` Hans Hagen
2021-05-18 16:44 ` Hans Hagen
2021-05-19 16:34 ` Hans Hagen
2021-05-19 16:49 ` Thomas A. Schmitz
2021-05-19 17:22 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-17 22:43 Tex " jbf via ntg-context
2008-06-03 7:10 TeX " M.guravage
2008-06-03 9:11 ` Taco Hoekwater
2004-07-10 17:01 jimarin
2004-07-12 7:17 ` Willi Egger
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=6c2d023a-4451-df59-44a7-8fa2184abc40@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).