From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Alan Braslau via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: bottlenecks
Date: Sat, 17 Dec 2022 22:35:04 +0100 [thread overview]
Message-ID: <4ea1eec7-5f88-6cf8-9f10-ad197e891610@freedom.nl> (raw)
In-Reply-To: <20221217141153.61b2bb14@boo.my.domain>
On 12/17/2022 10:11 PM, Alan Braslau via ntg-context wrote:
> With lots of MetaPost, lots of references, lots of figures, lots of tables, lots of bibliography entries, lots of chemical structures, ...
>
> mkiv lua stats > node memory usage: 2491 attribute, 76 boundary, 84 dir, 1167 glue, 85 gluespec, 430 glyph, 242 hlist, 333 kern, 32 math, 647 mathspec, 238 par, 328 penalty, 88 rule, 2 temp, 100 vlist, 18 whatsit
ok, i need to figure out where these lists come from (could be harmless,
(mp) caching or so)
> mkiv lua stats > runtime: 17.027 seconds, 578 processed pages, 578 shipped pages, 33.946 pages/second
that's quite decent i guess
> system | total runtime: 68.547 seconds of 68.576 seconds
the fact that we have multiple runs make any optimization count for more
than on a single run
thanks for testing
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-17 21:35 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 ` Hans Hagen via ntg-context [this message]
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=4ea1eec7-5f88-6cf8-9f10-ad197e891610@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).