From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why LuaMetaTex is so slow?
Date: Fri, 19 Jan 2024 11:49:44 +0100 [thread overview]
Message-ID: <6333b165-027d-49ed-9a99-58f83e6da676@xs4all.nl> (raw)
In-Reply-To: <b8c905da-8e41-45d1-aef4-be33aad90057@fiee.net>
On 1/19/2024 11:00 AM, Henning Hraban Ramm wrote:
> Am 19.01.24 um 10:31 schrieb Hans Hagen:
>> (that said: luametatex runs fine on my mobile phone)
>
> What’s the smallest/oldest device someone tried LMTX on?
> (We were joking about “Hans’ thermostate and Alan’s fridge“…)
> Would it run on some 8 bit homecomputer? (I’d guess the RAM is too
> limited, and loading from datasette would need hours…)
>
> Just curious.
The smallest i have here is a https://en.wikipedia.org/wiki/RCA_1802
which actually was a very nicely designed thing (also powers the
hubble); processors never became cleaner. Now, as the kit I used only
had 512 bytes ram (later 2K or so) it really learns one how to program
efficiently (thihk of writing a simple game, save and load from cassette
player, etc in that space; dynamic adaptive functions and such) and you
know where I'm coming from'(later pascal and modula).
That said: luametatex has a smaller memory footprint than luatex
although nodes are way bigger but even that won't make it run well on an
8 bit processor, assuming it can address 32 bit mem.
Context mkii started on 4.7 Mhz intel (386) so now we're 1000 times
faster but performance gain is not linear. After all, tex has to compete
with other applications running at the same time (browsers, remote
clients, media apps, web polling apps, zoom, etc.) so it's kin dof
amazing that it actually performs okay.
What boosted performance is for instance ssd's. What might boost is ddr5
memory but that has to catch up with ddr4 first. What also boosted
luametatex is cpu cache. I remember when taco and I moved to the math
part we noticed a drop in performance, until machines got updated with
larger cache. We'd just crossed some magic threshold.
Actually, I kind of assume that we're stuck with cpu performance but
nevertheless luametatex became faster. It helps to develop on an older
machine and not on a yearly updated one as that obscures matters. (Not
that I'd not like a faster machine, but that comes at a steep price.)
Hans
ps. In the tranmsition from pdftex to luatex to luametatex one should
not underestimate Taco's effort of going from basically unreadable and
useless C output by web2c (pascal -> c) to what became the luatex C code
base (with embedded original documentation). From that we added more
functionality gradually over a decade till luametatex spun off, which
then lead to quite a bit of refactoring again (but trying to maintain
the spirit of how tex is programmed).
-----------------------------------------------------------------
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://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-19 10:53 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
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 [this message]
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=6333b165-027d-49ed-9a99-58f83e6da676@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).