From: Mikael Sundqvist <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Why LuaMetaTex is so slow?
Date: Thu, 18 Jan 2024 20:08:23 +0100 [thread overview]
Message-ID: <CAHy-LL8fF7_LYvnn+z3XiMpGuN3UNxAXb__X_G37vh-Q+9T7Xg@mail.gmail.com> (raw)
In-Reply-To: <CALJ_jGR3SLaRj0JHSVQpN33Fh0-fni1t4JS6jR9o0r-i7Le5gw@mail.gmail.com>
Hi,
On Thu, Jan 18, 2024 at 7:58 PM Shiv Shankar Dayal
<shivshankar.dayal@gmail.com> wrote:
>
>
>
>
>> In comparison to LaTeX with LuaHBTeX, ConTeXt with LuaMetaTeX is
>> lightning fast.
>>
>> pdfTeX is 8bit, and Knuth’s plain TeX is very low level – for a fairer
>> comparison, try the TeXbook on LuaMetaTeX (I don’t know if “plain” works
>> though).
>
>
> I understand that why it is slow, but the problem is that the difference is too high.
> My book has lots of math, so perhaps that is the reason.
>
For what it is worth, I have a math book (lots of math and references
back and forth and some figures) and the 300 pages compiles in around
10s, so 30 pages/s. I don't have too much to compare with, and that is
a bit slower than your 40 pages/s (but 40*30 is 1200 and not 450), but
I consider that pretty fast.
One thing you can try is \enableexperiments[fonts.compact] (as it
sounds, it is still experimental).
Also, if you do not provide any example code, it will be difficult for
people to guess how _you_ can speed up your compilation (if at all).
/Mikael
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-01-18 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 17:24 [NTG-context] " Shiv Shankar Dayal
2024-01-18 17:47 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-01-18 18:40 ` Henning Hraban Ramm
2024-01-18 18:56 ` Shiv Shankar Dayal
2024-01-18 19:08 ` Mikael Sundqvist [this message]
2024-01-18 19:31 ` Hans Hagen
2024-01-18 23:34 ` Aditya Mahajan
2024-01-19 0:09 ` Hans Hagen via ntg-context
2024-01-19 0:33 ` Aditya Mahajan
2024-01-19 8:51 ` Hans Hagen
2024-01-18 22:15 ` Bruce Horrocks
2024-01-19 9:31 ` Hans Hagen
2024-01-19 10:00 ` Henning Hraban Ramm
2024-01-19 10:35 ` Taco Hoekwater
2024-01-19 10:49 ` Hans Hagen
2024-01-19 18:13 ` Bruce Horrocks
2024-01-19 18:30 ` Hans Hagen
2024-01-18 20:55 ` Gavin via ntg-context
2024-01-18 21:33 ` Joseph Wright
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=CAHy-LL8fF7_LYvnn+z3XiMpGuN3UNxAXb__X_G37vh-Q+9T7Xg@mail.gmail.com \
--to=mickep@gmail.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).