From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: luatex on the garden
Date: Fri, 31 Aug 2018 20:56:48 +0200 [thread overview]
Message-ID: <89801642-f622-cf9b-da54-9c1f3d23d81c@gmx.es> (raw)
In-Reply-To: <38506050-6923-1cd4-b825-e3a7044a1e58@xs4all.nl>
On 08/31/2018 10:27 AM, Hans Hagen wrote:
> [...]
> A lot of work went into this release and we hope that it's worth it. I
> will rmove some older code paths in a few weeks (less code that way) so
> then beta's will assume the new binary is used.
Many thanks for the new LuaTeX, Hans.
I have used for a document (http://blog.ousia.tk/0005/#context-source),
which hashes (with both SHA512 and SHA256) 38 external files.
With the previous beta, it took about 160s to completely generate the
PDF output (always with --purgeall). With the current beta, it only took
9.9s, which is a huge improvement.
I know that this might be the most favorable case for the new LuaTeX
improvements, but this is even faster than using the external binaries
that the OS (Linux64 in this case) provides.
This faster compilation could be also decreased when LuaJIT includes
bitwise operators, couldn’t it be?
Many thanks for your excellent work again,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-08-31 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 8:27 Hans Hagen
2018-08-31 18:56 ` Pablo Rodriguez [this message]
2018-08-31 19:33 ` Hans Hagen
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=89801642-f622-cf9b-da54-9c1f3d23d81c@gmx.es \
--to=oinos@gmx.es \
--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).