Speeding up LaTeX compilation

Question

Usually I don't mind about LaTeX's compilation speed, because a paper of less than 20 pages is compiled rather fast. However, I am working on a large document - A report with more than 80 pages. Compilation times are starting to slow me down. I saw the couple of answers here on this topic, but most of my graphics are external and I don't use Tikz. As a matter of fact, I'm not sure what's slowing the compilation down, other than the amount of text and required layout.

1. What's your best speeding-tex-up trick, other than externalizing graphics and pre-compiling the preamble?
2. How can I know what's slowing TeX down?

Answer 1

Beware of Greeks bearing gifts... Apparently, the nice todonotes package that I used dragged Tikz along with it, and introduced a major slowdown. Switching to simple marginpars gave a nice speedup. It should be noted that this package is a performance Trojan horse.

Answer 2

large documents start with pages >500 ... Create a script which runs:

pdflatex -draftmode file
bibtex file # or biber
makeindex file.idx # if needed
makeindex -s style.gls ...# for glossary if needed
pdflatex -draftmode file
pdflatex file

The compilation can now be speedup if you run bibtex/makeindex/... only when there were changes in this area. Can be detected with a diff for the auxiliary files.

Answer 3

I think the most effective way to save time is to avoid compiling the document time and time again. Compilations are often not really needed, when we change several words or a simple equation.

For large documents, we can split them into small pieces using \include command. Then \includeonly helps us to compile the only piece we are interested in, leaving the whole compilation to the last stage.

For complex tables or graphs made by TeX, put them into seperate TeX files first to verify the code, then add them to the document.

Sometimes compilation options may affect the speed. pdflatex -interaction=batchmode foo is often faster than pdflatex foo, this avoid scrolling informations. There may be more, say, xelatex -no-pdf foo is faster than xelatex foo, if it isn't the last round.

Answer 4

If you are using XeLaTeX, a substantial amount of time is spent gzipping data with highest compression (9) in the xdvipdfmx command.

~$ xdvipdfmx --help
…
-z number   Set zlib compression level (0-9) [9]
…

For me, on a 90 page document:

~$ time xelatex -interaction=nonstopmode Thesis.tex
…
real    0m6.056s
~$ ls -lh Thesis.pdf 
… 6,0M … Thesis.pdf

Without compression:

~$ time xelatex -interaction=nonstopmode -output-driver='xdvipdfmx -z0' Thesis.tex
…
real    0m2.417s
~$ ls -lh Thesis.pdf 
… 142M … Thesis.pdf

That is ~60% time saved but 23× bigger. Ok, some compression is clearly needed. My sweet spot:

~$ time xelatex -interaction=nonstopmode -output-driver='xdvipdfmx -z3' Thesis.tex
…
real    0m2.957s
~$ ls -lh Thesis.pdf 
… 6,9M … Thesis.pdf

That is 0.5s for compression or some 16% of the total time, as opposed to the majority of the time with default settings. I can usually live well with the 15% bigger file size. Of course, it does make sense to use -z9 for the final build.

I did not use XeTeX but assume the same scenario applies.

Answer 5

The most useful trick I know is: do not do textual changes and layout changes at the same time, but make a clear division between them.

I first fix up all the text issues (there is hardly any need to recompile during that cycle) and only afterwards worry about layout and page breaks. The separation means that in the second cycle, I can usually tackle more than one display problem simultaneously.

The second most useful trick I know is: buy a computer with a faster CPU.

Precompilation of the header will only save you some startup time, but does nothing for consecutive pages, so the effect diminishes as your document grows.

Answer 6

Although the original post is rather old, I just stumbled upon this issue myself with a 100+ pages project with lots of figures.

If you're still working on the document and the resulting PDF file size is less important, you may try adding the following primitives at the beginning of your document

\pdfcompresslevel=0
\pdfobjcompresslevel=0

This significantly increased the PDF file size for me, but in turn reduced compilation time to (not by) about 34%. If you're done editing and want to compile the final version, just comment out these lines.

This is somehwat related to I have a name now's post, but doesn't require the command line and appears to be independent of whether you're using pdflatex or other engines.

Best, r.

Answer 7

Here is a tip:

Beamer+graphics is a time-consuming combination that I revisit every now and then when preparing presentations. What I do is keep all my graphics in a directory images that is actually a symbolic link to either images-hires or images-lowres. The latter is a script-generated directory with a copy of each image in image-hires but with a considerable resize transformation.

This process could be even smarter with a small preamble that checks the draft option of the document class and sets the correct path with \graphicspath. But I haven't done it because I didn't know this macro before and I am not very skilled at LaTeX/TeX macros and magics.

Answer 8

When you need to iterate on something (say, the formatting of an equation), a quick and dirty but very effective trick is to comment out the bulk of the document using:

\iffalse

all the stuff you don't need to compile every time...

\fi

then you can focus in on the particular section you are working on, until you've got it just right with a tight edit/compile loop.

Then uncomment the rest of the document.

Answer 9

Regarding your first question: the most noticeable speedup I've witnessed so far can be achieved by compiling to DVI instead of PDF. You may not be able to do that depending on the packages you use, however, but you could give it a try.

Answer 10

Personally, I use the -interaction=batchmode option to prevent verbose output. Also, for the first runs (except the last), you can use -draftmode option:

-draftmode
   Sets \pdfdraftmode so pdfTeX doesn't write a PDF and doesn't read 
   any included images, thus speeding up execution.

In case of error ($? -ne 0), it is sufficient to tail the log file. You can see the full code on Github.

Answer 11

Math Accents

Math accents can slow down a compilation. To speed up a document with many of these you can use the \accentedsymbol command defined in amsxtra subpackage of the amslatex package. In the example below, \vx can be used for \vect{x} but will not take the time required to place the accents (arrows on bold symbols for example). Note that since the typesetting is done out of context, some issues can arise (the size will not be small in a superscript for example), so for the final version you should redefine \accentedsymbol to simply define a macro that will get expanded everywhere in context.

\usepackage{amsxtra}
%\renewcommand\accentedsymbol[2]{\def#1{#2}}  % Uncomment for final version
\accentedsymbol{\vx}{\vect{x}}

Note that there are limits to how many symbols you can store this way.

Kpathsea

Not really a LaTeX issue per se, but kpathsea can be a huge performance hit if you are recursively searching directories and/or your ls-R databases are not up-to-date. You can see what it is doing by setting

export KPATHSEA_DEBUG=1

before you run latex. If it is searching many places, then this can be a huge slow-down. Details can be found in the manual. (I had a huge performance hit when I accidentally recursively linked a texmf tree deep within another tree for a package I was writing.)

Answer 12

Don't load inputenc and/or fontenc if they are not necessarily needed because:

The inputenc–fontenc combination seems slow and cumbersome, but it’s safe.

cited from Why bother with inputenc and fontenc?

Answer 13

It is not about "speeding up" but "how to work when latex is really slow".

I use kile+okular.

1. In the setting of okular uncheck "reload document on file change".
2. Add "reload button" to the toolbar of okular

After that you can continue to read pdf file, and reload it only when it is ready.

Answer 14

1. For a large document, I would suggest making seperate tex files and using \include{filename} to include these files into the main file. Then, in the preamble, you can add command \includeonly{filename1} to start working on the file. There has been a quick fix around to comment out the code at \include to temporarily remove the files you are not using, but it disturbs the aux files. So, it's not recommended.
2. Do not use todonotes package. It seems that i am not the only one who has an slowing down issue with this package.
3. Use draftmode. It specially helps when you have a lot of images and it can be declared in the very beginning. I choose to keep the declaration code in individual lines so it's simpler to just comment/uncomment the lines to switch draftmode on/off.

\documentclass[
12pt,
draft
]{article}

4. Don't compile every now and then. It's probably not applicable to you or many others here, but people recently migrating from WYSIWYG softwares like MS word are more used to seeing a compiled document everytime. It helps to get used to read the TEX code for how it is.

Answer 15

Depending on your file system, file read/write times might be slowing *latex down. If you are on a Unix like system, you could keep all your resources in RAM. To do so you would first mount a ramdisk:

mkdir /mnt/ramdisk;
sudo mount -t tmpfs -o size=64M tmpfs /mnt/ramdisk;

(be sure to pick a sufficiently large size so your entire project including all resources will fit)

Than every time you want to rebuild, you would run:

rsync --archive --human-readable --progress --update --exclude=\"thesis.pdf\" . /mnt/ramdisk; 
cd /mnt/ramdisk; 
pdflatex thesis.tex; 
cd /path/to/your/thesis;

This syncs all changes you may have made since the last run (using rsync) and than invokes *latex on that copy of your files. The output is found in /mnt/ramdisk/thesis.pdf. I will simply open this in my viewer but at least in some circumstances one might like to sacrifice some time and copy the result to the original location (cp /mnt/ramdisk/thesis.pdf thesis.pdf).

This worked really well for me, as I used this setup to bring down compile times from 45 to 3 seconds.

Answer 16

I have a little tip:

If you want to include lots of figures, try to make them in vector graphics (.svg, .pdf, .ps), rather than raster graphics (.jpg, .png).

In my practice, a latex file containing 20 pages & 22 figures takes 56 seconds to compile when all figures are in .png, but only 4 seconds when I replace all of them with .pdf figures.

This may help people like me preparing latex draft for journal publication, since plots made with Python Matplotlib, IDL, Matlab, Origin or Excel can be easily exported in .pdf format.

Answer 17

So, What I did to handle the costly compilation is that, I first split up the document into the several chapters and every chapter into its own file, using the \input command. The main document has all the \input statements.
Example:
Inside the main_file.tex

\input{chapter1}
\input{chapter1_results}
\input{chapter2}
\input{chapter3}

---

Only the ones that are critical are not commented out. 'chapter1_results.tex' takes a lot of time to compile because of presence of figures. So I do the following, and its fast as hell.

Inside the main_file.tex

\input{chapter1}
%\input{chapter1_results}
\input{chapter2}
\input{chapter3}

Answer 18

I made a new Python script/module/package for this purpose.

https://github.com/user202729/tex-fast-recompile

(unlike other answers, this does not actually speed up the compilation, but it makes the PDF appear faster after the source code is edited)

I'll quote a section from the readme/documentation:

How does it work?

The principle is very simple. Notice that while the user want fast refresh, the file does not change very frequently.

As such, we start the compiler before the file has changed to process the "preamble", then when the file changed we continue processing the rest of the file.

A graph for illustration:

Before:

(each * represents a file change, |--.--| represents a compilation where the . marks where the preamble processing is done)

+----------------------------------------------------> Time
     *          *                *           *
     |--.--|    |--.--|          |--.--|     |--.--|

After:

+----------------------------------------------------> Time
     *          *                *           *
     |--.--|--. --|--.           --|--.      --|

It can be easily seen that after the change, it only takes 2 instead of 5 time unit from when the file is saved to when the change is reflected in the PDF.

---

Note on other known methods: (mentioned in the comments etc., collected here for convenience)

Precompile the preamble

There are a few guides on this.

• Ultrafast PDFLaTeX with precompiling

  • answer has a guide of mylatexformat package
  • links to: https://web.archive.org/web/20160712215709/http://www.howtotex.com:80/tips-tricks/faster-latex-part-iv-use-a-precompiled-preamble/

• https://tex.stackexchange.com/a/521482/250119

  example how to precompile preamble with LuaTeX without mylatexformat (tested and does work)

• https://tex.stackexchange.com/a/269052/250119

  • tutorial of mylatex package (note that this is older than mylatexformat)

• How to speed up pdflatex for a very large document on MacOS X?

  • mentions latexdaemon
  • answer has a guide of precompiling without mylatexformat package
  • links to: https://web.archive.org/web/20150406152732/https://magic.aladdin.cs.cmu.edu/2007/11/02/precompiled-preamble-for-latex/

Note

Precompile header with xelatex explain it doesn't work with XeTeX/LuaTeX in some cases.

Externalize TikZ graphics

Refer to Externalizing TikZ-Images takes very long

You can also parallelize TikZ-externalize for some extra performance, refer to https://tikz.dev/library-external#tikz/external/mode (mode=list and make) for instruction; or refer to https://tex.stackexchange.com/a/151255/250119.

Answer 19

Guess I'm pretty late to the party, but I use something that has not been mentioned here. My documents contain a significant amount of very high quality images, so I make two copies of the image file with one low resolution jpg and one high resolution png. I rename the files such that they have the suffix LOWRES.jpg or HIGHRES.png (I use png because that's what the image making software exports to). And I made a macro in TeXstudio that switches between the two image files.

This is some of my images in my images folder of my tex document:

And in my tex document I would have something like \includegraphics[width=5cm]{methanalLOWRES.jph} And the suffix would be changed by the macro below depending on whether I want to quickly compile a draft or compile to the best quality (which takes a significantly longer time). I use this in conjunction with \includeonly and it has signficantly reduced the compilation time.

%SCRIPT

scope = editor.document().cursor(0, 0, -1);

if (editor.search("HIGHRES.png", "g") > 0) {
  editor.replace("HIGHRES.png","g",scope,"LOWRES.jpg");

} else {
  if (editor.search("LOWRES.jpg", "g") > 0) {
    editor.replace("LOWRES.jpg","g",scope,"HIGHRES.png");
  }
}

I added this as a script macro on TeXstudio, so I am unsure if it will work on TeXmaker or other LaTeX editors, but the script is fairly basic and you should be able to implement your own for your own situation.

EDIT: I use this website to resize my images https://bulkresizephotos.com. I simply just make the width 800px, and it outputs a lower resolution jpg file which I download (and unzip if multiple files were submitted). I believe imagemagick can do something similar, but I have not looked into it.

I just saw YuppieNetworking's answer above, which is very similar to my answer, nonetheless I will keep my answer here should someone want to use the script

Answer 20

It is slow and will get even slower (which is an empirically well-established issue for all software development and not only for LaTeX). As usual, the ultimately best way may be to improve the architecture and the source code of (La)TeX and its packages and clean up the messy code in the process. That is, rewrite everything from scratch (which seems to be a project attainable only for folks having both finances and decades to spend on typesetting for the rest of their lifetime), starting with the goals and the documentation (i.e, how things should be). Outdated interfaces might be left out in the process, which, ultimately, would lead to a different and incompatible typesetting system.

The way out is to become a serious typesetting developer or to learn to live with what you get, in particular, slow compilation.

Not being a serious LaTeX developer, I have two versions of any of my large books: a draft version and a clean version. A book has two main files (say, draft.tex and clean.tex, where draft.tex defines my own macro \draft and inputs clean.tex). The program latex compiles the draft version quickly into DVI (sometimes followed by dvips), and lualatex/xelatex compiles the clean version slowly into PDF. Moreover, the document source is split into many files so that I can edit them while both latex and lualatex/xelatex run in the background. The only disadvantage is that your document source will likely have to contain several occurrences of \ifdefined\draft…\else…\fi (most often in the preamble and seldom in the main text), e.g., when loading different fonts and hyperlink-related packages.

Answer 21

There's this solution...

First, the disadvantages

• only works on POSIX systems
• requires LuaLaTeX
• somewhat cumbersome (for now)
• requires shell-escape and manually install some Lua library
• may fail to work for weird reasons, or damage your computer

The only advantages are...

• real incremental compilation! ^(*)
• cheaper than BaKoMa ^(†)
• supports LuaLaTeX

^(*): My attempts to use precompiled preamble (which is basically user-written format file) in LuaLaTeX has all failed, partially because Lua states and some other things cannot be dumped. _{maybe I should just switch back to pdflatex for the speed, especially now I am better at forcing TeX to do what I want} ^(†): There's now WYSIWYG editing though. (unfortunately)

---

The basic idea is to use fork() to spawn new process when part of the file change, instead of re-run it from scratch.

Proof of concept code:

%! TEX program = lualatex
\documentclass[12pt]{article}
\usepackage[paperheight=5cm,paperwidth=5cm,margin=0.6cm]{geometry}
\usepackage{luacode}
\usepackage{luapackageloader}
\begin{document}

% you can write some LaTeX here too

\begin{luacode*}

-- load the package
package.path = "/usr/share/lua/5.3/?.lua;/usr/share/lua/5.3/?/init.lua;/usr/lib/lua/5.3/?.lua;/usr/lib/lua/5.3/?/init.lua;./?.lua;./?/init.lua"
package.cpath = "/usr/lib/lua/5.3/?.so;/usr/lib/lua/5.3/loadall.so;./?.so"
local posix=require "posix"

function copyfile(source, target)
    local infile=io.open(source, "rb")
    local outfile=io.open(target, "wb")
    outfile:write(infile:read("*all"))
    infile:close()
    outfile:close()
end

--first backup the partial PDF content
copyfile(tex.jobname..".pdf", "backup-"..tex.jobname..".pdf")
copyfile(tex.jobname..".log", "backup-"..tex.jobname..".log") -- strictly speaking this is not necessary

while true do
    local pid = posix.fork()
    if pid == 0 then
        -- is child, compile b.tex
        break
    else
        -- is parent
        posix.wait(pid) 
        print("======== Press enter to recompile ========")
        io.read()
        -- **critical**: restore the partial PDF content
        copyfile("backup-"..tex.jobname..".pdf", tex.jobname..".pdf")
        copyfile("backup-"..tex.jobname..".log", tex.jobname..".log")
    end
end

\end{luacode*}

\input{b.tex}

\end{document}

First create a file named b.tex, put in some content.

Then run lualatex a.tex where a.tex is the main file (above).

When you edit b.tex, press enter in the lualatex process. It will regenerate a.pdf instantaneously... as long as b.tex isn't too long.