From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mf via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: bottlenecks
Date: Sun, 18 Dec 2022 14:49:20 +0100 [thread overview]
Message-ID: <a3a45a49-1d64-de5e-7364-2a95ba38033f@xs4all.nl> (raw)
In-Reply-To: <92ef9cc3-c83f-cacd-2eb8-b8e4df7fffdf@fastwebnet.it>
On 12/18/2022 2:14 PM, mf via ntg-context wrote:
> ...
So we gained a lot in the meantime.
> mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf,
> texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf,
> firasans-bolditalic.otf, firasans-regular.otf,
> firasans-regularitalic.otf, firasanscondensed-bold.otf,
> firasanscondensed-regular.otf, garamondpremrpro-bdit.otf,
> garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf,
> garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf,
> garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf,
> garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf,
> myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf,
> myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf,
> quivira.otf, sileot.ttf
> mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 533
> instances, 501 shared in backend, 6 common vectors, 495 common hashes,
> load time 0.196 seconds
How does that report with compact font mode?
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-18 13:49 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 ` 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 ` Hans Hagen via ntg-context [this message]
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=a3a45a49-1d64-de5e-7364-2a95ba38033f@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).