3 ms·
It takes 180s to import Statistics, PlutoUI, Images and OffsetArrays in Pluto on this Macbook Pro with 32GB that is a couple of years old, while the fans are go
by kitsune_ 6y ago
It takes 180s to import Statistics, PlutoUI, Images and OffsetArrays in Pluto on this Macbook Pro with 32GB that is a couple of years old, while the fans are going crazy. If I'm unlucky a worker process will seg fault. All in all the interactive / REPL part (even with stuff like Revise) is kind of a let down thanks to the slow precompilation / lack of caching? I like it, but I really don't see how it is ever going to replace Matlab, R or Python if these issues aren't addressed.
- eigenspace 6y agoI assume that's including precompilation, otherwise something is seriously wrong with your computer. Precompilation can take a while, but it's cached between sessions, so it should be much faster the second time. Also, in version 1.6, we have multithreaded precompilation which happens at installation time instead of when you first try to load the package. This makes it much faster.
- ku-man 6y agoJulia people say "in version 1.6... precompilation... is much faster". But they said the same when version 1.2 was released, same when 1.3, same with 1.4, and with 1.5, do you see a trend here?. It's clear the precompilation issue was never solved, otherwise it wouldn't be "fixed" in every single release.
- Acur 6y agoJust checked. On my slightly dated laptop the import of these packages in Pluto takes 5 seconds with Julia 1.6. In general 1.6 is a huge improvements in compilation times and usability for me.
- pkofod 6y agoWhat does "32GB" have to do with it? Why would a worker process segfault in this scenario?