From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: bottlenecks
Date: Sat, 17 Dec 2022 17:02:30 +0100 [thread overview]
Message-ID: <82ba8edb-7ade-690b-9bac-017e775e3cf1@fiee.net> (raw)
In-Reply-To: <d267d095-f860-6fbc-f781-7e13fad613e7@freedom.nl>
Am 16.12.22 um 21:02 schrieb Hans Hagen via ntg-context:
>> (2)
>> This is a 720 page novel (first run with this LMTX version, some fonts
>> were still uncached):
>>
>
>> mkiv lua stats > runtime: 19.275 seconds, 720 processed pages, 720
>> shipped pages, 37.355 pages/second
> so what if you add to the top
>
> \enableexperiments[fonts.compact]
ok, updated to latest LMTX, first run, all fonts still uncached:
mkiv lua stats > runtime: 19.025 seconds, 720 processed pages, 720
shipped pages, 37.846 pages/second
system | total runtime: 73.873 seconds of 73.964 seconds
real 1m13,971s
user 1m10,581s
sys 0m2,312s
next run, with fonts.compact:
mkiv lua stats > runtime: 19.327 seconds, 720 processed pages, 720
shipped pages, 37.254 pages/second
system | total runtime: 19.353 seconds of 19.453 seconds
real 0m19,461s
user 0m18,966s
sys 0m0,386s
without fonts.compact:
mkiv lua stats > runtime: 19.252 seconds, 720 processed pages, 720
shipped pages, 37.398 pages/second
system | total runtime: 19.283 seconds of 19.379 seconds
real 0m19,385s
user 0m18,943s
sys 0m0,380s
minimal difference.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-17 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 17:10 bottlenecks Hans Hagen via ntg-context
2022-12-16 19:36 ` bottlenecks Henning Hraban Ramm via ntg-context
2022-12-16 20:02 ` bottlenecks Hans Hagen via ntg-context
2022-12-16 21:08 ` bottlenecks Rik Kabel via ntg-context
2022-12-16 22:07 ` bottlenecks Hans Hagen via ntg-context
2022-12-17 0:05 ` bottlenecks Rik Kabel via ntg-context
2022-12-17 9:48 ` bottlenecks Hans Hagen via ntg-context
2022-12-17 15:05 ` bottlenecks Rik Kabel via ntg-context
2022-12-17 17:21 ` bottlenecks Hans Hagen via ntg-context
2022-12-17 21:11 ` bottlenecks Alan Braslau via ntg-context
2022-12-17 21:35 ` bottlenecks Hans Hagen via ntg-context
2022-12-18 21:35 ` bottlenecks Alan Braslau via ntg-context
2022-12-17 16:02 ` Henning Hraban Ramm via ntg-context [this message]
2022-12-17 17:43 ` bottlenecks Hans Hagen via ntg-context
2022-12-18 13:14 ` bottlenecks mf via ntg-context
2022-12-18 13:19 ` bottlenecks mf via ntg-context
2022-12-18 13:49 ` bottlenecks Hans Hagen via ntg-context
2022-12-18 15:21 ` bottlenecks mf via ntg-context
2022-12-18 15:27 ` bottlenecks 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=82ba8edb-7ade-690b-9bac-017e775e3cf1@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).