From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Is your ConTeXt too slow?
Date: Fri, 8 Nov 2002 16:51:30 +0100 [thread overview]
Message-ID: <20021108165130.07852018.morawski@gmx.net> (raw)
In-Reply-To: <20021108132814.GD9042@math.sf.edu>
On Fri, 8 Nov 2002 08:28:14 -0500
Jan Hlavacek <jhlavacek@sf.edu> wrote:
> On Fri, Nov 08, 2002 at 11:03:48AM +0100, Jens-Uwe Morawski wrote:
> > On Fri, 08 Nov 2002 09:30:56 +0100
> > Hans Hagen <pragma@wxs.nl> wrote:
> >
> > > At 09:36 PM 11/7/2002 +0100, Jens-Uwe Morawski wrote:
> > > >gnome-terminal: 2 min 18 sec
> > > >konsole (KDE-terminal): 1 min 30 sec
> > > >xterm: 1 min 5 sec
> > > >directly on the console
> > > > (no X-Windows): 58 sec
> > > >
> > > >Don't ask me for reasons, but if your ConTeXt is too
> > > >slow, ask yourself if you run it on the right terminal -)
> > >
> > > maybe no ls-R file is found and consulted, resulting in a full scan of the
> > > texmf file structure.
> >
> > No, no. TeX finds its files very fast. I could improve that with a smaller
> > texmf-tree, but 1+ min for the job is IMO okay; it runs 3xConTeXt,
> > 2xTeXUtil and 2xMetaPost. The problem is the terminal program. It seems
> > that the drawing of those many messages on the terminal needs much time.
> > If i use a slow terminal, i.e. gnome-terminal, then the runtime increases.
> Did you try to run context with output redirected to a file? How long
> does that take?
>
> try texexec yourfile.tex > logfile
ahh, interesting idea. Now it is independent from the used terminal and a run
needs about 50 seconds.
Jens
next prev parent reply other threads:[~2002-11-08 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 20:36 Jens-Uwe Morawski
2002-11-08 8:30 ` Hans Hagen
2002-11-08 10:03 ` Jens-Uwe Morawski
2002-11-08 13:28 ` Jan Hlavacek
2002-11-08 15:51 ` Jens-Uwe Morawski [this message]
2002-11-08 16:01 ` Hans Hagen
2002-11-09 10:28 ` Henning Hraban Ramm
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=20021108165130.07852018.morawski@gmx.net \
--to=morawski@gmx.net \
--cc=ntg-context@ref.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).