From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reducing compile time
Date: Tue, 24 Feb 2009 09:10:36 +0100 [thread overview]
Message-ID: <49A3AB7C.2030909@elvenkind.com> (raw)
In-Reply-To: <49A32AA7.7060608@googlemail.com>
Mohamed Bana wrote:
> maybe someone should research LuaJIT; http://luajit.org/
The fine print on LuaJIT:
* Only x86 (i386+) CPUs are supported right now (but see below).
That is the first, main reason why luajit is not included in
luatex yet. The other reason is that we don't expect that much
improvement because most of the lua code inside luatex is not
running at full interpreter speed anyway: mkiv is spending much
of its time in creating tables and table keys and the garbage
collector (we benchmarked this) neither of those task will
benefit from luajit.
There would be some speed gain, but not a lot. I am waiting for
luajit 2.0 and hoping it will support more architectures.
Best wishes,
Taco
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-24 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 17:16 Alan Stone
2009-02-23 17:36 ` Alan Stone
2009-02-23 17:54 ` Wolfgang Schuster
2009-02-23 19:57 ` Alan Stone
2009-02-23 20:26 ` Alan Stone
2009-02-23 20:40 ` luigi scarso
2009-02-23 23:34 ` Hans Hagen
2009-02-23 20:37 ` Wolfgang Schuster
2009-02-23 18:38 ` Taco Hoekwater
2009-02-23 23:00 ` Mohamed Bana
2009-02-24 8:10 ` Taco Hoekwater [this message]
2009-02-24 8:48 ` Hans Hagen
2009-02-23 23:27 ` 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=49A3AB7C.2030909@elvenkind.com \
--to=taco@elvenkind.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).