ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Duane Johnson <canadaduane@gmail.com>
To: ntg-context@ntg.nl
Subject: Recommendations for Speed?
Date: Sat, 15 Sep 2007 14:53:08 -0600	[thread overview]
Message-ID: <C5BDE8B7-3D2A-4AD5-9C56-5EB2B57428CE@gmail.com> (raw)

Hello,

I've been perusing the list archives for a couple of days now, and  
reading up on articles (such as Hans' regarding optimizing in TeX and  
eTeX) to find guidance on a handful of decisions.  Our company makes  
a web-based publishing solution called MemoryPress.com that uses  
conTeXt for on-demand creation of PDFs which are then converted to  
jpeg format for display in a web browser.

We are currently looking into ways to speed things up and since many  
of you are far more qualified than I am in this area, I wondered if  
you might advise me on the following:

1. Is there a way to keep TeX in-memory (i.e. as a server or daemon  
process) so that it doesn't have to load and reload fonts and the  
environment?  Our system makes repeated requests for typeset  
documents and we are wondering if there's a way to remove the  
overhead of re-running pdftex.

2. Among the many different command-line TeX options, what might  
optimize for speed?  I've done some rudimentary benchmarking and  
found that executing etex (without conTeXt) is much faster than  
texexec, and wondered if there is any advice in this area.  Is there  
any way to shave off some of the overhead of using conTeXt?

3. I've noticed that there is some kind of caching going on (tui/tuo  
files?) that helps speed things up after the first run.  How can I  
best take advantage of this facility?  What kinds of things will  
require TeX to start from scratch, vs. use some or all of this cached  
information?

4. Are there any other areas I should consider when looking for ways  
to use TeX as an on-demand typesetting engine?

Thank you,

Duane Johnson
Programming Manager
FamilyLearn
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2007-09-15 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 20:53 Duane Johnson [this message]
2007-09-17  8:07 ` Taco Hoekwater
     [not found] <mailman.1.1190023202.9795.ntg-context@ntg.nl>
2007-09-17 14:30 ` Duncan Hothersall

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=C5BDE8B7-3D2A-4AD5-9C56-5EB2B57428CE@gmail.com \
    --to=canadaduane@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).