Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/144193
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 26 Unrelated FailuresAs of commit dc7617d with merge base b7bef1c ( NEW FAILURE - The following job has failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Attention! native_functions.yaml was changedIf you are adding a new function or defaulted argument to native_functions.yaml, you cannot use it from pre-existing Python frontend code until our FC window passes (two weeks). Split your PR into two PRs, one which adds the new C++ functionality, and one that makes use of it from Python, and land them two weeks apart. See https://github.com/pytorch/pytorch/wiki/PyTorch's-Python-Frontend-Backward-and-Forward-Compatibility-Policy#forwards-compatibility-fc for more info. Caused by: |
|
PR is not ready yet to merge, but I'll mark it as ready for review to get some comments from you before proceeding further. There is still some things to optimize like launching a kernel to deal with syrk and trsm in parallel instead of in loops which I will tackle in the following days |
|
Added more optimizations but still slower than CPU 😞 Comments about improving speed are very welcome |
|
I compare implementations like this: |
|
@Isalia20 your PR has been successfully reverted. |
This reverts commit 727ae13. Reverted #144193 on behalf of https://github.com/malfet due to Alas, inductor changes broke inductor tests, see https://hud.pytorch.org/hud/pytorch/pytorch/aa4a1ff027316c6ad850180cfc20c3962eafb4e4/1?per_page=50&name_filter=inductor%20%2F%20linux-jammy-cpu ([comment](#144193 (comment)))
This PR was reopened (likely due to being reverted), so your approval was removed. Please request another review.
|
removed the op from fallback(originally had there before annotating linalg cholesky with CompImplicitAutograd, wrote devices like CUDA, CPU, Meta and thats why I had to have it originally in the fallback) Tests should pass now but I suggest running the workflow here before merging @malfet |
|
Hmm still failing. This is interesting. I'm not really sure why it's failing though. I looked into the test but don't see any cholesky ops in it. Any suggestions? |
|
Some of the PRs still had the issue with levit after reverting this so we can say that issues weren't caused by this. Maybe we can merge? @malfet |
|
bump |
|
@malfet Can we merge this? Want to submit another PR with speeding this up a lot |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Rebase failed due to Command Raised by https://github.com/pytorch/pytorch/actions/runs/12971799472 |
|
@Isalia20 do you mind rebasing this PR, because as of right now I could not get a clear signal. (Though I can always try merging it and see what will happen...) |
|
Tried rebasing but there are lot of commits, so I just decided to create a new one checking out from main |
Requested in #77764 Closed #144193 due to a lot of conflicts when rebasing Pull Request resolved: #145701 Approved by: https://github.com/malfet
Requested in pytorch#77764 Closed pytorch#144193 due to a lot of conflicts when rebasing Pull Request resolved: pytorch#145701 Approved by: https://github.com/malfet
Requested in #77764
PR is still in draft because it needs some cleanups and optimizations to get to cpu performance the least. Tasks:
upper=Truework, onlyupper=Falseworks nowcc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov