-
-
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
Performance difference between local Ref (allocated once) and a local float #20452
Labels
performance
Must go faster
Comments
4 tasks
I believe this is #16969 and #15369. We are just hitting the cache harder and running more instructions for an otherwise very cheap loop. Note that |
yuyichao
added a commit
that referenced
this issue
Jul 5, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 5, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 5, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
to yuyichao/julia
that referenced
this issue
Jul 5, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix JuliaLang#20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 8, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 9, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 9, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
to yuyichao/julia
that referenced
this issue
Jul 9, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix JuliaLang#20452
yuyichao
added a commit
that referenced
this issue
Jul 9, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 9, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 10, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 15, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
to yuyichao/julia
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix JuliaLang#20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 17, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 22, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 22, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 24, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
yuyichao
added a commit
that referenced
this issue
Jul 27, 2017
This can obtain escape information with much higher precision than what we can currently do in typeinf. However, it does not replace the alloc_elim_pass! in type inference either since this cannot handle objects with reference fields. Fix #20452
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Timing differences between summing into a local Ref (allocated once) vs a local float.
No difference when adding 1.0 a billion times
Ref
takes 50% more time when addingrand()
a billion timesThe text was updated successfully, but these errors were encountered: