From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: If you really absolutely need more capacity, you can ask a wizard to enlarge me
Date: Thu, 9 Sep 2021 10:12:48 +0200 [thread overview]
Message-ID: <9fa1de4c-f8fd-ff56-8645-2b3099a06d2c@xs4all.nl> (raw)
In-Reply-To: <CAK9ODgSC=XiQxQDck=CwDmaYKogeRxomXOV8Laj18Kq13abvpw@mail.gmail.com>
On 9/9/2021 12:52 AM, Marcus Vinicius Mesquita via ntg-context wrote:
> Dear list,
>
> In the MWE below, ConTeXt lmtx throws an error with the message in the
> title:
>
> \starttext
> \startluacode
>
> local upperlimit = 90000
>
> context.starttabulate({ "|l|l|l|" })
> for i=1,upperlimit do
> context.NC()
> context("word 1")
> context.NC()
> context("word 2")
> context.NC()
> context("word 3")
> context.NC()
> context.AR()
> end
> context.stoptabulate()
>
> \stopluacode
> \stoptext
>
> But it compiles with no problems with MKIV.
>
> context version: 2021.09.06 11:47
>
> How to avoid this with lmtx?
In luatex there is also a max on configured memory usage but because in
luametatex we have larger nodes you hit limits earlier. Also, the memory
allocation in luametatex is somewhat different (larger nodes are
compensated by savings elsewhere so in the end mem usage for this run is
similar).
luatex luametatex
pages 2196 2196
pps/s 8 11
time 278 195
mem 1.1G 1.1G
now, luametatex reports
tex memory > bumping category 'node' succeeded, details:
all=400500000 | ini=0 | max=50000000 | mem=44500000 | min=1000000 |
ptr=-843956 | set=50000000 | stp=500000 | top=43999999
you can bump the the max in the configuration file and also the step. As
you can see, luametatex runs quite a bit faster on this test but that is
due to other differences between the two engines.
The reason why it does run on my machine is that i have this:
\enableexperiments [tabulatesparseskips]
\enableexperiments [tabulateusesize]
this makes tabulate a bit more efficient in terms of node usage so i
stay some 20% below the configured max .. you can try to run with this
option. Of course adding more text will also demand more mem but then
you can always bump the max (in a configuration file in texmf-local or
so; maybe some day i will add a --huge flag to the runner).
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-09-09 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 22:52 Marcus Vinicius Mesquita via ntg-context
2021-09-09 8:12 ` Hans Hagen via ntg-context [this message]
2021-09-10 8:55 ` Marcus Vinicius Mesquita via ntg-context
2021-09-10 11:45 ` Marcus Vinicius Mesquita via ntg-context
2021-09-10 11:49 ` Hans Hagen via ntg-context
2021-09-10 12:36 ` Marcus Vinicius Mesquita via ntg-context
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=9fa1de4c-f8fd-ff56-8645-2b3099a06d2c@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).