[tex-live] Identifying the cause of slow compilation

Zdenek Wagner zdenek.wagner at gmail.com
Wed Mar 11 12:46:39 CET 2015

Hi Phil,

it seems to me that your TEXINPUT is not optimized,, it searches file by
disk lookup instead of default database lookup (if the components contain
!! as Markus wrote). The difference is thus the performance of the file
system. It is difficult to say why VM is faster, it would be important to
know whether it locates the files on its virtual disk or on the host disk.
Anyway, in plain TeX the difference should not be as pronounced as in LaTeX
where typically a lot of packages and other support files have to be
loaded. In plain TeX you read usually just the format, tfm files and your
document. You can try to use kpsewhich to locate a file and measure
required time.

Zdeněk Wagner

2015-03-11 12:18 GMT+01:00 Markus Kohm <komascript at gmx.info>:

> > How should I go about identifying the cause of the bottleneck in the
> > slow system ?
> - Compare TEXMF and the components of TEXMF like TEXMFDIST. Missing "!!"
> could
> slow down file searching.
> - Ask kpsewhich for other texmf.cnf using `kpsewhich -a texmf.cnf'.
> Use the KPATHSEA_DEBUG and TEXMFLOG to get more information about file
> searching. See `texdoc kpathsea', section 8.3 and 8.4 for more information
> about this.
> Markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20150311/5200ecd4/attachment.html>

More information about the tex-live mailing list