-
-
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
QR Decomposition Extremely Slow Converting to Float64 Matrix #29846
Labels
linear algebra
Linear algebra
Comments
Specifying the type parameter |
Thanks for the work around! That worked for what I was doing. Note that |
andreasnoack
added a commit
that referenced
this issue
Oct 30, 2018
LQ and Hessenberg to Matrix Fixes #29846
andreasnoack
added a commit
that referenced
this issue
Oct 31, 2018
LQ and Hessenberg to Matrix Fixes #29846
andreasnoack
added a commit
that referenced
this issue
Oct 31, 2018
LQ and Hessenberg to Matrix Fixes #29846
KristofferC
pushed a commit
that referenced
this issue
Nov 12, 2018
KristofferC
pushed a commit
that referenced
this issue
Dec 12, 2018
KristofferC
pushed a commit
that referenced
this issue
Feb 11, 2019
KristofferC
pushed a commit
that referenced
this issue
Feb 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems converting a qr decomposition Q matrix to a Float Matrix takes high-degree polynomial time at best.
Seems like a bug. I don’t remember having this problem on earlier versions (I am using 1.01 on Windows 10). Granted my laptop is pretty slow, but this is worse than matrix inversion, so the performance doesn’t make a lot of sense to me.
Output:
0.260873 seconds (120.00 k allocations: 145.569 MiB, 1.49% gc time)
2.115116 seconds (480.00 k allocations: 1.022 GiB, 3.70% gc time)
6.812497 seconds (1.08 M allocations: 3.372 GiB, 4.46% gc time)
15.563167 seconds (1.92 M allocations: 7.901 GiB, 3.08% gc time)
Version Info:
Also on discourse:
https://discourse.julialang.org/t/qr-decomposition-extremely-slow/16946?u=clinton
The text was updated successfully, but these errors were encountered: