ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context vs texinfo
Date: Thu, 08 Jul 2010 09:32:43 +0200	[thread overview]
Message-ID: <4C357F1B.9080005@elvenkind.com> (raw)
In-Reply-To: <AANLkTimLecJAy3hbInzLVkv-zFqzsBLjiF44qVtf7cbv@mail.gmail.com>


Hi,

Shiv Shankar Dayal wrote:
> Hi,
> 
> I was using context and I had to wait for 16 seconds for one run
> approximately. I switched to texinfo and it barely takes 2 seconds.

A whole 2 seconds? That's ridiculously slow! I just tried to print a
document with  'cat | lpr' and it took much less than a tenth of a
second! :)

> Can you please explain the diffrence? I know context is complex but still?

Seriously: you gave the first half of the answer yourself. The second
half is that texinfo is very simple. Yes, context is quite a bit slower
thanks to extra complexity.

I am not going to list all of the things context can do that texinfo
cannot as that would take the better part of an hour, but there
are a few other reasons as well:

* context usually needs three runs the very first time you process
a document (but typically only one or two runs after that) and it
does these consecutive runs automatically. It keeps running tex
until there are no more runs needed, and this sometimes (well,
often, to be honest) means that it does one run too many. But one
run too much is still a lot better than a wrong link.

* context typically is set up to use much larger values for the
internal memory arrays, and this results in a slower runtime. You
can actually speed up context by reducing its memory footprint
to just what is needed for your own typical document types
(dont forget to regenerate the formats).

Best wishes,
Taco

___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2010-07-08  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08  6:54 Shiv Shankar Dayal
2010-07-08  7:29 ` luigi scarso
2010-07-08  7:32 ` Taco Hoekwater [this message]
2010-07-08 10:25   ` Hans Hagen
2010-07-08  7:41 ` R. Bastian
2010-07-08  7:52 ` 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=4C357F1B.9080005@elvenkind.com \
    --to=taco@elvenkind.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).