From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reducing compile time
Date: Mon, 23 Feb 2009 21:37:42 +0100 [thread overview]
Message-ID: <2CC9BE52-D687-4044-8F38-44F71771CEA2@gmail.com> (raw)
In-Reply-To: <326847810902231157kc49bd83i8df988abc0ee28be@mail.gmail.com>
Am 23.02.2009 um 20:57 schrieb Alan Stone:
>> - does using \doifundefined{myMacro}{...} shorten tex runs/compile
>> time ?
>>
>> In which way?
>
> As I don't know/understand what happens between (Lua)TeX runs, to
> keep macro
> definitions in memory.
The only way to use information from a previous run is to use the
auxiliary
files or buffers. Macros are defined at each run again but you
shouldn't care
here about the performance unless you use a very big private module.
> - what are the features to avoid for shortest compile times ?
>>
>> Depends on your document and what do you want.
>
> My question was intended in a generic way, aka if you use
>
> - these features ... expect longer or significant longer compile
> times, or
> - these features ... generate the longest compile times.
As Taco mentioned, try to avoid \switchtobodyfont and use \definedfont
or \definefont instead. You can also gain a few (micro)seconds when you
run TeX in batchmode (no terminal messages).
Natural Tables are quite slow and it's sometimes worth to take a look
if you can use table or tabulate.
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-23 20:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 17:16 Alan Stone
2009-02-23 17:36 ` Alan Stone
2009-02-23 17:54 ` Wolfgang Schuster
2009-02-23 19:57 ` Alan Stone
2009-02-23 20:26 ` Alan Stone
2009-02-23 20:40 ` luigi scarso
2009-02-23 23:34 ` Hans Hagen
2009-02-23 20:37 ` Wolfgang Schuster [this message]
2009-02-23 18:38 ` Taco Hoekwater
2009-02-23 23:00 ` Mohamed Bana
2009-02-24 8:10 ` Taco Hoekwater
2009-02-24 8:48 ` Hans Hagen
2009-02-23 23:27 ` Hans Hagen
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=2CC9BE52-D687-4044-8F38-44F71771CEA2@gmail.com \
--to=schuster.wolfgang@googlemail.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).