From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lmtx
Date: Tue, 2 Apr 2019 21:03:24 +0200 [thread overview]
Message-ID: <D2D0988A-FA58-4C3A-AFF6-1146C8285BF4@elvenkind.com> (raw)
In-Reply-To: <b7987020-fed5-bbda-83be-797e7d589efa@xs4all.nl>
Hi,
> On 2 Apr 2019, at 11:05, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> - It is hard to be conclusive about performance but for instance the luatex manual processes a bit faster with lmtx as does the test suite. A gain in performance on very demanding documents is also observed by Alan and Thomas. Normally one can expect a similar performance. However, the memory footprint could be a bit smaller.
For sure the ConTeXt now loads and initialises a lot faster. With that trivial issue.tex test
file by Arthur I get these timings (after a few ‘warmup’ runs).
MkIV (This is LuaTeX, Version 1.09.3 (TeX Live 2019/dev)):
mkiv lua stats > stored bytecode data: 444 modules (0.445 sec), 93 tables (0.021 sec), 537 chunks (0.466 sec)
...
mkiv lua stats > runtime: 0.888 seconds, 1 processed pages, 1 shipped pages, 1.126 pages/second
system | total runtime: 1.391 seconds
real 0m1.646s
user 0m1.476s
sys 0m0.115s
LMTX:
mkiv lua stats > stored bytecode data: 456 modules (0.243 sec), 93 tables (0.016 sec), 549 chunks (0.259 sec)
...
mkiv lua stats > runtime: 0.559 seconds, 1 processed pages, 1 shipped pages, 1.789 pages/second
system | total runtime: 0.655 seconds of 0.725 seconds
real 0m0.731s
user 0m0.601s
sys 0m0.084s
Impressive!
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-04-02 19:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 9:05 lmtx Hans Hagen
2019-04-02 19:03 ` Taco Hoekwater [this message]
2019-04-02 20:11 ` lmtx Henri Menke
2019-04-02 20:19 ` lmtx Hans Hagen
2019-04-02 20:30 ` lmtx Henri Menke
2019-04-02 20:47 ` lmtx Hans Hagen
2019-08-05 12:38 lmtx Hans Hagen
2019-12-12 0:37 lmtx Hans Hagen
2019-12-12 5:28 ` lmtx Otared Kavian
2019-12-12 6:04 ` lmtx Otared Kavian
2019-12-12 10:08 ` lmtx Hans Hagen
2019-12-12 6:36 ` lmtx Richard Mahoney | Indica et Buddhica
2019-12-12 16:59 ` lmtx Pablo Rodriguez
2019-12-12 20:13 ` lmtx Pablo Rodriguez
[not found] <mailman.310.1576128525.1207.ntg-context@ntg.nl>
2019-12-12 23:48 ` lmtx Jeong Dal
2019-12-13 8:39 ` lmtx Otared Kavian
[not found] <mailman.1.1576234801.28358.ntg-context@ntg.nl>
2019-12-13 19:29 ` lmtx Jeong Dal
2020-06-19 10:11 lmtx Hans Hagen
2020-10-30 22:29 lmtx Hans Hagen
2020-10-31 2:50 ` lmtx Jairo A. del Rio
2020-11-02 19:43 ` lmtx Hans Hagen
2021-01-18 18:20 lmtx Hans Hagen
2021-01-19 10:57 ` lmtx Floris van Manen
2021-01-19 11:10 ` lmtx Hans Hagen
2021-01-19 11:31 ` lmtx Jano Kula
2021-01-19 19:12 ` lmtx Jan U. Hasecke
2021-01-19 23:03 ` lmtx Hans Hagen
2021-02-19 12:32 lmtx Hans Hagen
2022-02-03 21:00 lmtx Hans Hagen 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=D2D0988A-FA58-4C3A-AFF6-1146C8285BF4@elvenkind.com \
--to=taco@elvenkind.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).