From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: much slower compilation with latest beta
Date: Mon, 24 Mar 2014 20:33:44 +0100 [thread overview]
Message-ID: <53308898.6090406@gmx.es> (raw)
Hans,
I’m afraid there might be something wrong with beta from 2014.03.24 00:52.
With a book I’m writing, either in complete (from a previous --purgeall)
or partial (from previous .tuc and .log files) compilation, the latest
beta needs 8 runs to compile a document. It takes about 140 secs with
luatex and about 100 with luajittex. Document source is exactly the same
in all cases.
The same document with beta from 2014.03.07 11:42 (sorry, I don’t have
the previous beta) requires a single run for a partial compilation which
about 12 secs. Total compilation needs 4 runs that take about 50 secs.
I think that the same may happen with the ConTeXt reference manual.
Since compilation is not direct, all statistics I can provide is that it
took 358.491 secs with latest beta from 2014.03.24 00:52. and 296.778
secs with previous beta from 2014.03.07 11:42.
I guess there might be a bug here.
Many thanks for your help,
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2014-03-24 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 19:33 Pablo Rodriguez [this message]
2014-03-25 1:02 ` Hans Hagen
2014-03-25 5:28 ` Pablo Rodriguez
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=53308898.6090406@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).