I have recently switched from Xe(La)TeX to Lua(La)TeX 1.0.4 (TeX Live 2017) in order to use font expansion feature of microtype package.

As a result, my compilation time increased dramatically. I confirmed that performance decrease is caused by LuaLaTeX itself, as removing microtype package doesn't speed the process.

For medium-size document (about 300 pages) I went from 1.9s compilation time with XeLaTeX to 4.2s seconds with LuaLaTeX.

It wouldn't it too bad if I run it only a handful of times, but I am doing manual adjustments to page breaking and hence I need to run it very frequently.

If I run LuaLaTeX only on 1 chapter (10 pages or so), I get PDF in 1.4s.

Is there any way to tell LuaLaTeX to only generate few pages around last edit point, or only a chapter in which edit took place? Ideally, it would preserve earlier part of the PDF file, so that pages do not move in PDF viewer, but anything after currently edited chapter can be ignored.

Additional information based on comments:

  • I am using Ubuntu 14.04 LTS 64-bit.
  • In case it matters, I edit my source files in Sublime Text 3.
  • I am not using cross-references or any "interactive" elements, which might affect or be affected by pagebreaking. Just plain, literal text.
  • For chapter headings I am using \chapter* with chapter numbers written manually.
  • 1
    @Arzigoglu Very interesting. Though, I am kind of addicted to Sublime Text, so probably would not use WinEdt anyway ;) – Rafal Jul 6 '17 at 12:36
  • 3
    How exact has the partly compilation to be? If you are fine tuning the page breaking then almost every other part of the document can influence it, e.g. through references, citation, acronyms, etc. – Ulrike Fischer Jul 6 '17 at 12:47
  • 2
    Then I would use \include and \includeonly to work on one chapter, or simply comment out the \input commands for the other chapters. – Ulrike Fischer Jul 7 '17 at 7:39
  • 1
    I realize it's a bit involved, but otftotfm can be used to get OTF fonts into pdflatex. If you just use one or a few fonts repeatedly, it may be worth it. See for example tug.org/TUGboat/tb27-2/tb87owens.pdf – Michael Palmer Jul 7 '17 at 15:05
  • 1
    1. If you have a feature request please create an issue at github 2. You may also have a look at the subfiles package, which sounds like it solves your problem (if you use that you should enable prereleases, because special support for that package has been added there) – r-stein Jul 11 '17 at 14:42

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.