ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why LuaMetaTex is so slow?
Date: Thu, 18 Jan 2024 19:40:53 +0100	[thread overview]
Message-ID: <acc5afdd-9089-490c-864e-fb72afc7da7f@fiee.net> (raw)
In-Reply-To: <e3c6e45e-3fb5-f460-26a3-9cc7aa4ac697@gmx.es>

Am 18.01.24 um 18:47 schrieb Pablo Rodriguez via ntg-context:
> On 1/18/24 18:24, Shiv Shankar Dayal wrote:
>> I can process TeXBook in almost an instant using PDFTeX which is about
>> 450+ pages but my math book takes around 30 seconds averaging ~40
>> pages/second.
> 
> Hi Shiv Shankar Dayal,
> 
> I guess that “The TeXbook” (having been written by Knuth himself) may be
> optimized for speed.
> 
> Your math book may use features (I’m guessing again) that require more
> resources than the features used by “The TeXbook”.
> 
>> Why LuaMetaTeX is so slow? How can I speed it up?
> 
> https://www.pragma-ade.com/general/manuals/musings.pdf#page=96 might
> explain why Lua(Meta)TeX is slower.
> 
> Other chapters in that document from Hans might give you some insight on
> the reasons why LMTX has to pay a price for being more feature-rich. I
> got such impression when I read it.
> 
> Just in case it might help,

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).

Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2024-01-18 18:44 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 [this message]
2024-01-18 18:56     ` Shiv Shankar Dayal
2024-01-18 19:08       ` Mikael Sundqvist
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=acc5afdd-9089-490c-864e-fb72afc7da7f@fiee.net \
    --to=texml@fiee.net \
    --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).