ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: betas
Date: Thu, 09 Jan 2014 19:29:59 +0100	[thread overview]
Message-ID: <52CEEAA7.3040701@wxs.nl> (raw)

Hi,

As some of you might have noticed, we're in transition to luatex 0.80
(currently 0.78.1). This binary is somewhat faster with respect to nodes 
without modification of Lua code, but it also provides an additional 
node field access mechanism. Luigi and I spent quite some time on 
getting that done and in the process some 70 context files were adapted 
(as we needed to test). However, it's likely that I have missed some 
needed changes. As both access mechanisms cannot be mixed, one has to be 
consistent in usage. Also, the somewhat faster (new) usage is more 
sensitive for errors so it has to be used with robust (proven) code 
(read: pluggable code can best use the traditional node field accessors 
which also have been sped up). And of course it only makes sense for 
very demanding cases (as stock luatex is already rather efficient now), 
think of devanagari (where we can get 50% faster) and complex arabic 
(some 25%). As ConTeXt spends > 50% of its time in Lua it might make a 
difference in other places too.

Anyway, for instance the 175 fonts-mkiv manual processes 10% faster due 
to this and sometimes more can be achieved (it really depends on how 
much Lua enhanced mechanisms are used). Roughly I get on my win 8.1 64 
bit laptop for the font manual:

10    sec luatex    0.77 with previous context code base
10.25 sec luatex    0.77 with current context code base
  9.00 sec luatex    0.78 with current context code base
  7.50 sec luajittex 0.78 with current context code base

(This manual loads quite some fonts in the process.)

In case you wonder why speed is an issue: it really matters when tex is 
used as a service, and I like fast edit-test cycles too. The target is 
to get 20 pps or more even for complex documents. It's not that hard to 
get 550 pps for simple 1000 page one-word-per page documents but when 
much more kicks in we quickly drop to 15-20 pps.

Also, Luigi and I also want to reach reasonable speeds on android phones 
(triggered by Harald's experiments at the context meeting) but that's 
another topic.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2014-01-09 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 18:29 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-07  8:52 betas Hans Hagen
2009-03-13 17:34 betas Hans Hagen
2009-03-13 17:54 ` betas luigi scarso
2009-03-13 18:05   ` betas Thomas A. Schmitz
2009-03-14  0:07     ` betas Yanrui Li

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=52CEEAA7.3040701@wxs.nl \
    --to=pragma@wxs.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).