ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Does MKIV take more time as MKII
Date: Mon, 14 Mar 2011 21:22:01 +0100	[thread overview]
Message-ID: <AANLkTi=X87x6mv3qKbEjwp+WCZ9b8VJj6+RXxtvXH0-6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=SDb9Y=drDYGdU6bhx4eKOy2J3bPWT2HZA+4qk@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2331 bytes --]

You can't have it Good, Cheap, and Fast all at once ;)

On Mon, Mar 14, 2011 at 8:52 PM, Mojca Miklavec <
mojca.miklavec.lists@gmail.com> wrote:

> On Mon, Mar 14, 2011 at 14:47, Cecil Westerhof wrote:
> >
> > Both did not work for me. But removing --purgeall from my script reduced
> the
> > time from 30 seconds to 10.
>
> When you don't use --purgeall, ConTeXt calculates different things
> (for example table of contents, cross-references etc.) and stores them
> to temporary files. Next time when you compile the same document
> without too many changes it simply reuses the old data.
>
> But if you remove the temporary files with --purgeall, ConTeXt has to
> recalculate everything from scratch. Out of curiosity I checked that
> on my own document and realized exactly the same thing. Compile time
> dropped from 27 to 9 seconds, but only because ConTeXt had to read and
> typeset the document three times (I thought it usually did it twice).
>
> If you remove all the temporary files and call context without
> --purgeall, it will also take 30 seconds to typeset everything; it is
> only the second and all the subsequent runs that finish the job
> faster.
>
> Mojca
>
> PS: You would get the same kind of behaviour in MKII (however if MKII
> only runs twice and if there is a speed factor of 1.5, you could
> declare MKII being "three times faster" which does make some
> difference when compilation time is long).
>
> PPS (not to be taken (too) seriously): But I wouldn't be surprized if,
> say, two years from now you would try to repeat the experiment just to
> find out that MKIV became faster. (Unlikely to happen, but imaging
> Taco coming to idea to use all the four processor cores of your new
> machine and Hans reducing the number of required runs from three to
> two plus some extra optimizations.)
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 3148 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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:[~2011-03-14 20:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 10:23 Cecil Westerhof
2011-03-14 11:44 ` Wolfgang Schuster
2011-03-14 11:48   ` Cecil Westerhof
2011-03-14 13:02     ` Aditya Mahajan
2011-03-14 13:34       ` Alan BRASLAU
2011-03-14 13:47         ` Cecil Westerhof
2011-03-14 19:52           ` Mojca Miklavec
2011-03-14 20:22             ` John Haltiwanger [this message]
2011-03-15  7:56             ` Henning Hraban Ramm
2011-03-16 16:39             ` Hans Hagen
2011-03-16 16:52               ` luigi scarso
2011-03-16 16:59                 ` Hans Hagen
2011-03-14 17:54 ` Philipp Gesang

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='AANLkTi=X87x6mv3qKbEjwp+WCZ9b8VJj6+RXxtvXH0-6@mail.gmail.com' \
    --to=john.haltiwanger@gmail.com \
    --cc=mojca.miklavec.lists@gmail.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).