Clearly lower optimization wouldn’t be faster always, or we would always use lower levels. As of version 1.5 it doesn’t need to be one global setting, and since we can tune I suggest changing the default. E.g. for some real-world 27 line script of mine (that uses three packages, e.g. CSV.jl) runs fo…

[image] Palli: I’ve been making PRs to packages with the new module-level low-optimization trick How are you benchmarking to make sure that your PRs does not introduce runtime regressions?

[image] kristoffer.carlsson: How are you benchmarking to make sure that your PRs does not introduce runtime regressions? I’m not (at least yet; for Revise, I’m just using it with the change and haven’t seen a difference). It’s up to the maintainer, and I mention a possible slowdown (I guess w…

About the superoptimizer: 1711.04422.pdf 333.36 KB If we can automatically derive compiler optimizations, we might be able to sidestep some of the substantial engineering challenges involved in creating and maintaining a high-quality compiler. Don’t get m…

I think the portion of compilation that gets “wasted” is a big part of this. It would be nice if you didn’t have to rely on PackageCompiler (which even then isn’t always perfect) to avoid having so much compilation repeated each time you restart the REPL/load a new script.

By “wasted” compilation (true in a sense) I think you mean “invalidations” that you can fix (to some degree with): [image] GitHub - timholy/SnoopCompile.jl: Making packages work faster with more... Making packages work faster with more extensive precompilation - GitHub - timholy/SnoopCo…

JIT compilation >> The application code is initially interpreted, but the JVM monitors which sequences of bytecode are frequently executed and translates them to machine code for direct execution on the hardware. @@ Just-in-time compilation - Wikipedia Otherwise A JIT compiler should operate on th…

[image] Jeff Bezanson remarks on LLVM "getting slower and slower" Internals Thx @ImreSamu , Support for A JIT compiler should operate on the Pareto rule principle "… for many outcomes, roughly 80% of consequences come from 20% of the causes (the “vital few”).[1] " @@ Pa…

Rethinking optimization, lower ok for all Julia code (for e.g. faster startup) as a default?

General Usage

Marc.Cox April 12, 2021, 3:26pm 8

Topic		Replies	Views
Julia optimization levels; and the case for less optimization, slower; faster compilation General Usage	0	1661	October 25, 2023
Implications of --compile=min and --optimize=0, for dummies Performance question , compilation , scripting	22	4361	March 12, 2021
Can Julia really be used as a scripting language? (Performance) Performance	69	8812	July 28, 2020
Julia vs R vs Python: simple MLE problem Optimization (Mathematical)	43	5481	April 5, 2019
Ensure Julia is used to its full power New to Julia question , first-steps	100	7520	December 11, 2020

Rethinking optimization, lower ok for all Julia code (for e.g. faster startup) as a default?

Related topics