From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luatex on the garden
Date: Fri, 31 Aug 2018 21:33:20 +0200 [thread overview]
Message-ID: <6b1f5c59-88ed-a296-94b8-86deda8361a7@xs4all.nl> (raw)
In-Reply-To: <89801642-f622-cf9b-da54-9c1f3d23d81c@gmx.es>
On 8/31/2018 8:56 PM, Pablo Rodriguez wrote:
> 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?
it's unlikely that that will happen (basically luajit stays 5.2 so
eventualy we might have to drop it) but if you do some extensive testing
you will notice that mkiv with luatex is not that much slower than
luajittex on regular documents (definitely the gap is becoming less)
luajit(tex) has some built in knowledge about its bit functions so it
can optimize them (just like math functions, which is why these
calculating benchmarks work out so well)
in context we use bitwise operators in luatex and the bit functions when
in luajittex (these operators are not used that frequently yet) and you
don't want to know the details
> Many thanks for your excellent work again,
Thanks.
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 / 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
___________________________________________________________________________________
prev parent reply other threads:[~2018-08-31 19:33 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
2018-08-31 19:33 ` Hans Hagen [this message]
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=6b1f5c59-88ed-a296-94b8-86deda8361a7@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).