4 ms·
Do y'all have a performance roadmap (or issue tracker tag?) that lists some optimizations that you foresee as julia matures? If not, I hope you and/or Jeff will
by bugsbunnyak 14y ago
Do y'all have a performance roadmap (or issue tracker tag?) that lists some optimizations that you foresee as julia matures? If not, I hope you and/or Jeff will do a blog post on this at some point! One key point of interest would be the split (obviously hand-wavy) between:
- llvm hotness that you don't use yet
- well-known techniques from HotSpot, Smalltalk, V8, etc.
- researchy optimizations that julia is particularly suited for?
This would be a nice resource for newcomers with a language bent, and also as a building block for your Google Summer of Code applications ;)
- StefanKarpinski 14y agoThat's a good idea. Jeff is the real compilers genius so I'll have to see if I can convince him to write a blog post along those lines. The bounds check stuff I mentioned above is one of the important planned optimizations. Another important move is making composite types immutable by default, which is surprisingly unstiffling, yet allows a large number of clever optimizations (stack allocation, memory layout optimizations). More playing around with llvm optimization passes could help and is pretty easy to do, but we haven't spent much time on that. Also lots of gc improvements (approximate ref counting, escape analysis).