5 ms·

What kind of speed do you see now?

by Sukera 6y ago

leephillips 6y ago
I’ve also been running the release candidates, and I get something like 6 seconds to first plot on my 2013 laptop, including the time for `using Plots` and the time to actually draw the first plot. A huge improvement; kudos to the developers.
MisterBiggs 6y ago
No idea if this is really a fair comparison but just to get a brief idea of current speeds: julia> @time let using Plots plot([sin, cos]) end 11.267558 seconds (17.98 M allocations: 1.114 GiB, 4.83% gc time) Versus Matlab which probably takes about 15 seconds just to open the editor but plotting is very fast. >> tic fplot( @(x) [sin(x) cos(x)]) toc Elapsed time is 0.374394 seconds. Julia is just about as fast as Matlab after the first run for plotting.
- siproprio 6y ago
  > Matlab which probably takes about 15 seconds just to open the editor Try this: matlab -nosplash -nodesktop -r "tic; fplot( @(x) [sin(x) cos(x)]); toc"
  - eigenspace 6y ago
    I believe that's still not going to capture the startup time of Matlab itself, right?
    - siproprio 6y ago
      It's faster than opening the editor, though.
  - cbolton 6y ago
    This took 25 seconds on my laptop (15 seconds the second time, when the filesystem was warm).
- dan-robertson 6y ago
  I wonder how much Julia could be helped with some uneval/image-saving magic. So when you run the repl you instead get a pre-built binary with plot already loaded and several common specialisations already compiled.
  - staticfloat 6y ago
    We call these "system images" and you can generate them with PackageCompiler [0]. Unfortunately, it's still a little cumbersome to create them, but this is something that we're improving from release to release. One possible future is where an environment can be "baked", such that when you start Julia pointing to that environment (via `--project`) it loads all the packages more or less instantaneously. The downside is that generating system images can be quite slow, so we're still working on ways to generate them incrementally. In any case, if you're inspired to work on this kind of stuff, it's definitely something the entire community is interested in! [0] https://github.com/JuliaLang/PackageCompiler.jl https://github.com/JuliaLang/PackageCompiler.jl
    - jpfr 6y ago
      Easy, you only have to add a handful of „battery included“ packages to the default system image. That however means that some packages get a preferred status in the Julia ecosystem.

What kind of speed do you see now?

by Sukera 6y ago

What kind of speed do you see now?

I’ve also been running the release candidates, and I get something like 6 seconds to first plot on my 2013 laptop, including the time for `using Plots` and the time to actually draw the first plot. A huge improvement; kudos to the developers.

MisterBiggs 6y ago

No idea if this is really a fair comparison but just to get a brief idea of current speeds: julia> @time let using Plots plot([sin, cos]) end 11.267558 seconds (17.98 M allocations: 1.114 GiB, 4.83% gc time) Versus Matlab which probably takes about 15 seconds just to open the editor but plotting is very fast. >> tic fplot( @(x) [sin(x) cos(x)]) toc Elapsed time is 0.374394 seconds. Julia is just about as fast as Matlab after the first run for plotting.

siproprio 6y ago
> Matlab which probably takes about 15 seconds just to open the editor Try this: matlab -nosplash -nodesktop -r "tic; fplot( @(x) [sin(x) cos(x)]); toc"
- eigenspace 6y ago
  I believe that's still not going to capture the startup time of Matlab itself, right?
  - siproprio 6y ago
    It's faster than opening the editor, though.
- cbolton 6y ago
  This took 25 seconds on my laptop (15 seconds the second time, when the filesystem was warm).
dan-robertson 6y ago
I wonder how much Julia could be helped with some uneval/image-saving magic. So when you run the repl you instead get a pre-built binary with plot already loaded and several common specialisations already compiled.
- staticfloat 6y ago
  We call these "system images" and you can generate them with PackageCompiler [0]. Unfortunately, it's still a little cumbersome to create them, but this is something that we're improving from release to release. One possible future is where an environment can be "baked", such that when you start Julia pointing to that environment (via `--project`) it loads all the packages more or less instantaneously. The downside is that generating system images can be quite slow, so we're still working on ways to generate them incrementally. In any case, if you're inspired to work on this kind of stuff, it's definitely something the entire community is interested in! [0] https://github.com/JuliaLang/PackageCompiler.jl https://github.com/JuliaLang/PackageCompiler.jl
  - jpfr 6y ago
    Easy, you only have to add a handful of „battery included“ packages to the default system image. That however means that some packages get a preferred status in the Julia ecosystem.