From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: TeX capacity exceeded
Date: Tue, 18 May 2021 18:44:51 +0200 [thread overview]
Message-ID: <c80729e2-f4bd-31ba-0530-155250c390be@xs4all.nl> (raw)
In-Reply-To: <109a5562-b863-1335-b6cd-db55399c7d6a@uni-bonn.de>
On 5/17/2021 11:43 PM, Thomas A. Schmitz wrote:
> Is texmfcnf.lua still the configuration file I need to look at for this
> kind of problem? Which variable could I change?
Normally not needed but this is the section for luatex:
["luatex.errorline"] = 250, -- no need to change
["luatex.halferrorline"] = 125, -- no need to change
["luatex.expanddepth"] = 10000, -- no need to change
["luatex.hashextra"] = 100000, -- rarely more is needed
["luatex.nestsize"] = 1000, -- often an error if more needed
["luatex.maxinopen"] = 500, -- i use 2000
["luatex.maxprintline"] = 10000, -- no need to change
["luatex.maxstrings"] = 500000, -- maybe sometimes
["luatex.paramsize"] = 25000, -- seldom
["luatex.savesize"] = 100000, -- often an error if more needed
["luatex.stacksize"] = 100000, -- often an error if more needed
not, in luametatex we have some more and also more control; this is what
the next version will support (the above method is how it currently
goes, max values that use the preset allocations steps)
["luametatex.errorlinesize"] = { size = 250 },
-- max = 255
["luametatex.halferrorlinesize"] = { size = 250 },
-- max = 255
["luametatex.expandsize"] = { size = 10000 },
-- max = 1000000
["luametatex.stringsize"] = { size = 500000, step = 100000 },
-- max = 2097151 -- number of strings
["luametatex.poolsize"] = { size = 10000000, step = 1000000 },
-- max = 100000000 -- chars in string
["luametatex.hashsize"] = { size = 250000, step = 100000 },
-- max = 2097151
["luametatex.nodesize"] = { size = 50000000, step = 500000 },
-- max = 50000000
["luametatex.tokensize"] = { size = 10000000, step = 250000 },
-- max = 10000000
["luametatex.buffersize"] = { size = 10000000, step = 1000000 },
-- max = 100000000
["luametatex.inputsize"] = { size = 100000, step = 10000 },
-- max = 100000 -- aka stack
["luametatex.filesize"] = { size = 2000, step = 200 },
-- max = 2000
["luametatex.nestsize"] = { size = 10000, step = 1000 },
-- max = 10000
["luametatex.parametersize"] = { size = 100000, step = 10000 },
-- max = 100000
["luametatex.savesize"] = { size = 500000, step = 10000 },
-- max = 500000
["luametatex.fontsize"] = { size = 250, step = 250 },
-- max = 100000
["luametatex.languagesize"] = { size = 250, step = 250 },
-- max = 10000
["luametatex.marksize"] = { size = 50, step = 50 },
-- max = 10000
One can just define the max if needed because we bump memory stepwise
(on demand). It depends on the kind of projects you have. One can also
sey { plus = 10000 } to add more to the set size without bothering about
existing values. Now, if you watch closely you'll see that most max
values are high already (initial values cannot be set) but token and
node memory as well as string related values can be set much larger.
However, it makes sense to limit. Actually for some scenarios one might
even want to go lower.
When you compare mkiv and mkxl you'll notice that we use less memory
anyway (for various reasons / optimizations). The format file is also
smaller (esp when you take into account that the mkiv one is zip
compressed and the lmtx one isn't).
But ... your problem was not related to the above.
The next upload will also mention detailed mem usage in the log file. If
you want to see how your document behaves you can say
\enabletrackers[system.usage]
at the top (is already there for a while).
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-18 16:44 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 [this message]
2021-05-19 16:34 ` Hans Hagen
2021-05-19 16:49 ` Thomas A. Schmitz
2021-05-19 17:22 ` Hans Hagen
-- 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=c80729e2-f4bd-31ba-0530-155250c390be@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).