From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: bottlenecks
Date: Fri, 16 Dec 2022 21:02:36 +0100 [thread overview]
Message-ID: <d267d095-f860-6fbc-f781-7e13fad613e7@freedom.nl> (raw)
In-Reply-To: <ec8156f4-d4a5-43bf-c51b-e1106c52f919@fiee.net>
On 12/16/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote:
> Am 16.12.22 um 18:10 schrieb Hans Hagen via ntg-context:
>> So the challenge is how to determine bottlenecks. Are there users on
>> this list that have document runs of more than 10 seconds (as
>> reference: the luametatex manual takes < 9 seconds for 350 pages and
>> loads plenty fonts and has many tables) or have many (small) runs and
>> are annoyed by the runtime? And if so, what does one guess are the
>> bottlenecks?
>
> (1)
> This is my 366 page ConTeXt book:
> mkiv lua stats > runtime: 30.592 seconds, 366 processed pages, 366
> shipped pages, 11.964 pages/second
> (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]
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 / 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-16 20: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 ` Hans Hagen via ntg-context [this message]
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 ` bottlenecks Henning Hraban Ramm via ntg-context
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=d267d095-f860-6fbc-f781-7e13fad613e7@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).