5

This question may seem like it's been asked a million times over, but the relevant questions tackle XeLaTeX or plain LaTeX. What I want to know is if moving any filesystems/file locations to a dedicated RAMdisk would help more quickly compile LuaTeX?

Reading the previous questions, it seems that the consensus is that it's basically the CPU/Intel processor that is the key bottleneck. However, this comment notes that when using certain fonts, the OS/filesystem performance does play a role as it affects font loading. I use LuaTeX exclusively as I have a self-made package which uses MinionMath and ArnoPro, as well as some other fonts for certain symbols. For this reason, and because of that comment, I'm wondering if maybe for this specific case moving some filesystems/file locations to the RAMdisk could be helpful in speeding up performance?

I understand that LuaTeX isn't as fast as other compilers, and especially my custom package is ridiculously demanding (LOTS of additional commands and customisations, and using otf fonts of ArnoPro in all sizes and types, and MinionMath font, as well as 13 other packages preloaded into it which are absolutely necessary -- trust me on this one!) so I understand that it will still be relatively slow. However, even having the time cut by half or a quarter would be great! So, would this idea work? And how would I go about it (i.e. which filesystems/locations specifically would I move)? I use Linux 17.1 Cinnamon if it helps. Thanks!

EDIT: Thanks to a good point about LuaJIT that was brought up, I found further commentary on the font debacle here. The comments in that specific thread are revealing, and help point out my problem with fonts specifically as the major issue, not the OS or compiler or etc. It's not clear that LuaJIT (with JIT on or off) would help the issue much, as font loading takes the vast majority of the time (probably with fontforge libraries or similar, no idea). That is the biggest issue. (Also, the links for downloading LuaJIT require a password now!)

  • 2
    Related: Tips for choosing hardware for best LaTeX compile performance -- answer indicates that disk I/O will get cached in memory pretty easily, and won't be significant. You could always build a 4GB ramdisk with mkdir /usr/local/texlive; mount -t tmpfs -o size=4G,mode=755 tmpfs /usr/local/texlive and see what happens if you install TL 2014 there versus to the regular disk. – Mike Renfro Jan 4 '15 at 1:57
  • 1
    "ridiculously demanding" in what sense? IO or CPU? Lua is very fast. Try luajittex (with and without jit enabled) to see if this speeds up things. But as with every performance question: measure it. It is hard to guess where the performance bottleneck is. You could even write your own font loader if you need more performance... – topskip Jan 4 '15 at 13:09
  • @topskip thank you for the information! Please see the question edited in response :) – airatin Jan 4 '15 at 23:46
  • @MikeRenfro Considering it is font loading that is the biggest issue, I don't see how installing texlive in the ramdisk would be of significant help? – airatin Jan 4 '15 at 23:46
  • Are your fonts not in the TL tree? If not, I'm wrong. – Mike Renfro Jan 5 '15 at 4:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.