ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Stephen Gaito <stephen@perceptisys.co.uk>
Subject: Re: Using ConTeXt-LMTX for modern Mathematically-Literate-Programming 1/2
Date: Wed, 2 Dec 2020 14:04:18 +0100	[thread overview]
Message-ID: <3d6c8bcd-00dd-e734-dbad-b70f0fb177be@xs4all.nl> (raw)
In-Reply-To: <20201202094029.695ba8b1@nn01>

On 12/2/2020 10:40 AM, Stephen Gaito wrote:

> Many thanks for your swift and helpful comments.
> 
> After some *very crude* tests using the `luametatex` and `luametafun`
> documents, I find that while I *can* stop effective processing at
> various points in the LuaMetaTeX pipeline, the time difference overall
> is not really significant enough to bother with this approach.
> 
> The principle problem is, as you suggested below, "stopping" the
> pipeline at the PDF stage (using for example the `pre_output_filter`)
> corrupted the `*.tuc` data which is for my purposes, critical.
> 
> Your comment was:
> 
>> but keep in mind that multipass data is flushed as part of the
>> shipout (because it is often location and order bound)
> 
> For the record, using the `append_to_vlist_filter` callback, I did
> manage to drastically reduce the "pages" (which were all blank, not
> surprisingly).
> 
> However, on my elderly desktop from 2008, both callbacks essentially cut
> only 6-8 seconds out of 18 seconds, for the `luametatex` document, and
> 190 seconds, for the `luametafun` document.

hm, on my 2013 laptop the luametatex manual needs 10 sec (i have all the 
fonts, so that includes a bunch) and a metafun manual should do about 20

a test on am M1 mini needs half those times as reported yesterday

i bet that on a modern desktop the luatex manual will do < 5 sec

> In the case of the `luametafun` document, it is the MetaFun/MetaPost
> processing which, of course, is taking a long time (as it should, the
> graphics computations represent important but complex computations).

One run or many due to xref? Maybe your machine has no significant cpu 
cache? Do you run from disk or ssd? How much memory?

> My ultimate goal is to parallelize the production of large, heavily
> cross-referenced, ConTeXt documents... more on this in a future email...
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
___________________________________________________________________________________

  reply	other threads:[~2020-12-02 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  9:51 Stephen Gaito
2020-11-30 18:59 ` Hans Hagen
2020-12-02  9:40   ` Stephen Gaito
2020-12-02 13:04     ` Hans Hagen [this message]
2020-12-03 10:35       ` Stephen Gaito
2020-12-03 11:15         ` Taco Hoekwater
2020-12-03 12:15           ` Hans Hagen
2020-12-03 17:08             ` Stephen Gaito
2020-12-03 16:53           ` Stephen Gaito

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=3d6c8bcd-00dd-e734-dbad-b70f0fb177be@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=stephen@perceptisys.co.uk \
    /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).