ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: [Fwd: [pdftex] pdftex 1.40]
Date: Wed, 03 Jan 2007 13:25:58 +0100	[thread overview]
Message-ID: <459BA0D6.2010102@wxs.nl> (raw)
In-Reply-To: <E1H20Vh-0006Tw-00@skye.ra.phy.cam.ac.uk>

Sanjoy Mahajan wrote:
> >From the texexec man page:
>
> --fast
>     Typeset the document(s) as fast as possible without causing
>     problems.
>
> --final 
>     Perform a final run without skipping anything. This option is
>     typically used with --fast.
>
> So --fast --final could be the pair of switches to add.  But I tried
> an experiment with mediocre results, using this test file:
>
> ====================== q.tex =================
> \doifnotmode{*last}{\pdfdraftmode=1}
> \starttext
> \completecontent
>
> \chapter{A}
> \dorecurse{500}{\input tufte\par}
>
> \chapter{B}
> \dorecurse{400}{\input tufte\par}
>
> \chapter{C}
> \dorecurse{100}{\input tufte\par}
>
> \stoptext
> ============================================
>
> I ran it with the attached Makefile, which produced this output:
>
>   ctxtools --purge --all > /dev/null
>   rm -f q.pdf
>   texexec --verbose --fast --final q.tex > run.log
>   Total runs    : 4 (counted by grepping run.log for running: pdfetex)
>   Draftmode runs: 3 (counted by grepping run.log for pdfdraftmode)
>   TeXExec | runtime: 7.987485
>
> Then I commented out the first line and reran it:
>
>   ctxtools --purge --all > /dev/null
>   rm -f q.pdf
>   texexec --verbose --fast --final q.tex > run.log
>   Total runs    : 4
>   Draftmode runs: 0 (just to check)
>   TeXExec | runtime: 8.307869
>
> So the draftmode saves 4% in the runtime.  But the fastest is to not
> use the draftmode and not use --final (which causes an extra run).
> Maybe I missing a trick, but the draftmode didn't save much time.  I
> guess I should make the test file read in a few huge images?
>   
try bigger stuff, say a file with some 100 meg pictures and 25 fonts ; that's what draftmode is for (one of those ideas that popped up during eurotex 2006 at our usual pdftex dev chat). 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  parent reply	other threads:[~2007-01-03 12:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 14:21 Taco Hoekwater
2007-01-02 14:32 ` Thomas A. Schmitz
2007-01-02 17:02 ` Peter Münster
2007-01-03  1:48   ` Aditya Mahajan
2007-01-03  1:59     ` Martin Schröder
2007-01-03 22:12       ` Hans Hagen
2007-01-03  7:26     ` Sanjoy Mahajan
2007-01-03 10:25       ` Martin Schröder
2007-01-03 12:25       ` Hans Hagen [this message]
2007-01-03 22:10     ` Hans Hagen
2007-01-03 22:45       ` Sanjoy Mahajan
2007-01-04  1:10         ` Hans Hagen
2007-01-04  1:12           ` Aditya Mahajan
2007-01-04  1:21             ` Martin Schröder
2007-01-04  2:00               ` Aditya Mahajan
2007-01-03 14:26 ` luigi scarso
2007-01-03 19:07   ` Hans Hagen
2007-01-04  8:13     ` luigi scarso

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=459BA0D6.2010102@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).