The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Jon Forrest <nobozo@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] eqn
Date: Fri, 04 Oct 2019 19:43:00 +0200	[thread overview]
Message-ID: <20191004174300.Ok_Nq%steffen@sdaoden.eu> (raw)
In-Reply-To: <389f5a69-e103-7ec3-9b95-3e6e294a86e6@gmail.com>

Jon Forrest wrote in <389f5a69-e103-7ec3-9b95-3e6e294a86e6@gmail.com>:
 |One slightly OT fact about TeX. On my 16GB, Core i7, SATA SSD
 |Lenovo T430s laptop running Fedora 30, it takes ~3 seconds to run TeX on
 |the ~900 page TeXBook. That's pretty fast. TeX contains all kinds of
 |code to make it fit in the constraints of a 1980s computer. I wonder
 |whether a redesign for a 2020 computer would be faster or slower.

It made a really huge difference whether you base upon the plain
TeX macros, maybe with epsf.tex for embedding .eps files, and
colordvi.tex for colors in slides, index and bibliography reviews
etc., or whether you use the huge LaTeX macros.  Also lazy loading
fonts added upon that, i finally added that and it saved a 1-2
second hang upon program startup (plain tex plus ~250kb single
file macro, plus the mentioned included) for each and every letter
that was sent out.

  % 00-05-31: new scheme to avoid waste. now a font is init only if it's used.
  % 2Compare (Cyrix 166+, 49MB, Linux 2.2.13-12, X 3.3.5):
  % | OLD                               | NEW                                   |
  % |-----------------------------------|---------------------------------------|
  % | 1178 strings out of 13013         | 1413 strings out of 13013             |
  % | 13106 string characters of 122154 | 17026 string characters of 122154     |
  % | 35574 words of memory of 263001   | 54220 words of memory of 263001       |
  % | 2086 multiletter of 10000+0       | 2321 multiletter of 10000+0           |
  % | 80647 font info for 276 fonts     | 20674 words of font info for 70 fonts |
  %   (out of 400000 for 1000)

 |I suspect, but can't prove, that classic [nt]roff might also
 |benefit in the same way. groff was written latter, so it might
 |suffer less.
 |
 |Jon
 --End of <389f5a69-e103-7ec3-9b95-3e6e294a86e6@gmail.com>

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  parent reply	other threads:[~2019-10-04 17:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  4:20 Larry McVoy
2019-10-04  4:35 ` Dave Horsfall
2019-10-04  5:12 ` George Michaelson
2019-10-04 13:43   ` Nemo
2019-10-04 14:57 ` aksr
2019-10-04 15:52   ` U'll Be King of the Stars
2019-10-04 16:12     ` Jon Forrest
2019-10-04 17:24       ` Adam Thornton
2019-10-04 18:55         ` Kurt H Maier
2019-10-04 17:43       ` Steffen Nurpmeso [this message]
2019-10-06  8:03       ` arnold
2019-10-04 19:02     ` Larry McVoy
2019-10-07 17:26     ` Seth J. Morabito
2019-10-07 19:14       ` Adam Thornton
2019-10-08 21:11         ` Seth Morabito
2019-10-04 19:25 ` Fabio Scotoni
2019-10-05  1:59 Doug McIlroy

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=20191004174300.Ok_Nq%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=nobozo@gmail.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).