-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
startup time #28092
Comments
This is an issue with startup time, or more generally compile time, and not performance (in the sense of throughput) in general. We are well aware of it; you can find more examples under the "latency" issue label. Work on this is ongoing, though currently we have to prioritize addressing the much longer delays that can happen when loading certain packages. |
@JeffBezanson it seems devs here are "close happy"? every single one of those issues you linked have been closed, and i would consider this issue far from fixed. julia is currently and order of magnitude (or more) slower than other popular languages. |
I didn't say the issue was fully resolved, I said it had a lot of history. For example in one of those issues the startup time was over 2 seconds, so perhaps we considered it fixed relative to that. We will continue to work on this. Please be patient. |
Doing something like #28075 would approximately half current startup time. https://asciinema.org/a/hMmHsdvVxqhQTkcO60uz1c23U for that PR vs status quo. |
Not to understate the issue here, but although Julia can indeed be used as a quick sripting language (I myself collect arXiv preprints using a quick Julia script), many of the most relevant applications of the language involve heavy computations, for which 0.5 secs is peanuts. I myself am already quite pleased with startup latency relative to the old times, and if @JeffBezanson says so, you can count on further improvements in that regard. |
Well, currently the startup time of 0.7 is higher than for 0.6. It would be nice if that could be fixed. |
Update: on my system this has now gone from about 0.5 sec to 0.2. |
On my system Julia 0.7 is still significantly slower than 0.6:
Version info:
|
Can you try build #28118 and report the results. |
Julia v0.7beta.152
Julia v0.7beta2.26
In the #28118 branch
Julia v0.6.1
EDIT: on a macbook pro with an Intel i7-7567U CPU @ 3.50GHz |
#28118 is not rebased on master, right? So then we might get below 100 ms, which seems to be a massive improvement. |
There is probably overlap that #28118 precompiled functions that are now instead lazily executed. I haven't checked how big that overlap is. |
I see, #28118 is already rebased. |
(I just pushed a rebased version) |
Rebased #28118 (best time of several)
Does that make sense?? |
If almost all |
I can confirm that #28118 is still much snappier than master, despite both launching equally fast. The |
I can confirm that Julia 0.7 is now faster than Julia 0.6.4:
Julia version used:
Good job! 👍 |
@ufechner7 thanks - it looks like it might be time to close this - as it appears julia is even faster than ruby now - i dont see any artifacts here http://ci.appveyor.com/project/JuliaLang/julia so looks like i will need to do a build myself before i can test this |
The assumption, that Julia would start faster than ruby is unfortunately wrong. It is still about five times slower. But from my point of view that's good enough for now, taken the huge runtime performance benefits into account.
I just have a fast computer. Nevertheless, from my point of view Julia 0.7 is already fast enough to be released. Further latency improvements can happen later. |
One thing worth noting is that at this point, we should probably not be measuring print time in start up as printing is kind of slow. Something like '1+1' might be a better test. |
You are right, in the 1+1 contest Julia 0.7 performs worse, it is about 7 times slower than ruby and even slower than Julia 0.6.4. And yes, without println performance improves, but I think it is more realistic to print a result than not.
So still room for improvement! |
I would just time |
Dup of #17285. Don't think we need to have both open. |
@KristofferC how can my issue be a duplicate of... my issue? |
Oh, mistake :) #17285 (updated post above) |
Compare with Perl:
Or Python:
Or PHP:
Or Ruby:
The text was updated successfully, but these errors were encountered: