I wonder, are there any concrete medium to long-term plans regarding opportunistic caching of generated binary code (separately per architecture, to support computing environments with mixed CPU generations, AVX versions, etc.)? I know this has been discussed many times, and I’m fully aware that th…

The high-level answer is caching machine code is very appealing and has been considered very often but it’s fairly tricky. As the compiler work priorities post that @dawbarton ’s linked to indicates, compiler latency is one of the very top priorities. If you’ve got any bright ideas on how to tackle t…

Thanks a lot for the quick update and the link to the compiler work priorities! I’m not sure I have a any bright solutions to offer - I do realize that it’s a tricky thing to get right (and stable) and I’m know people with much deeper insight into the compiler have been thinking about this in depth…

I think having a mature and easy-to-use PackageCompiler which is part of the stdlib would be a great substitution for full-blown caching in many use cases. The biggest problem with Julia right now is not just that we have to recompile when using the REPL but that the methods for creating static (or…

I wouldn’t see AOT compilation so much as a substitute for caching, it’d rather say it’s orthogonal, since (as you say) the target are mainly non-interactive/non-development use cases. But it’s definitely a thing that people who I introduce to Julia ask about a lot: “If we have the code ready and wa…

Quite right; AOT compilation and caching for better interactive latency are orthogonal issues. But caching is just one possible solution to the latency problem, and I suspect it may not be the best. Caches need to be invalidated, and when that happens you lose all the benefit. I continue to consider…

The seductive thing about caching is that it would allow doing all the fancy optimizations that everyone loves all the time like we do now while still supposedly solving the latency problem. But the best approach to fixing most latency issues is still probably the tried-and-true tiered JIT approach. …

Plans regarding caching of generated code?

Internals & Design

dawbarton December 6, 2018, 2:25pm 2

Take a look at Compiler work priorities for a recent update from Stefan; I think it answers your question (though maybe not the fine detail).

Topic		Replies	Views
Per module runtime generated reloadable usrimg.jl Internals & Design proposal	2	1012	June 30, 2017
A prototype of `pkgimage` binary cache system for reducing latency General Usage	3	1279	August 12, 2022
Can Just-In-Time also be made to be Just-Once Internals & Design	3	883	October 9, 2018
Caching Bytecode/Binary for Dynamic Modules in Embedded Context General Usage	2	310	December 22, 2023
Questions about Compiler and Compiling Modules New to Julia	21	2276	January 17, 2019

Plans regarding caching of generated code?

Related topics