-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Use ninja to speed up build #5088
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
Conversation
|
Accidentally closed PR, reopen it. |
mrwyattii
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jinzhen-lin this is a great improvement in compile time for all the ops (~18 min --> ~10 min)!
|
@jinzhen-lin, thanks for improving the PR. Can you please resolve the formatting issues? |
Done. |
This should be resolved now. Thanks @jinzhen-lin - this speeds up our nv-pre-compile-ops builds by roughly 2x. |
Deepspeed have too many ops now, and it take too many time to pre-build all ops. I notice deepspeed disabled `ninja` 4 years ago (deepspeedai#298) and I think we should consider enable it now. The issue mentioned in deepspeedai#298 can be solved by resolving `include_dirs` to absolute path. --------- Co-authored-by: Logan Adams <114770087+loadams@users.noreply.github.com> Co-authored-by: Logan Adams <loadams@microsoft.com> Co-authored-by: Olatunji Ruwase <olruwase@microsoft.com> Co-authored-by: Michael Wyatt <michaelwyatt@microsoft.com>
deepspeedai#5192 reports an issue with the latest DeepSpeed release (0.13.3) related to pre-compilation and the recently re-enabled `ninja` support in deepspeedai#5088. Reverting to disabling `ninja` by default, but users can still enable it with `DS_ENABLE_NINJA=1` until we can further debug to understand the problem.
Deepspeed have too many ops now, and it take too many time to pre-build all ops. I notice deepspeed disabled `ninja` 4 years ago (deepspeedai#298) and I think we should consider enable it now. The issue mentioned in deepspeedai#298 can be solved by resolving `include_dirs` to absolute path. --------- Co-authored-by: Logan Adams <114770087+loadams@users.noreply.github.com> Co-authored-by: Logan Adams <loadams@microsoft.com> Co-authored-by: Olatunji Ruwase <olruwase@microsoft.com> Co-authored-by: Michael Wyatt <michaelwyatt@microsoft.com>
deepspeedai#5192 reports an issue with the latest DeepSpeed release (0.13.3) related to pre-compilation and the recently re-enabled `ninja` support in deepspeedai#5088. Reverting to disabling `ninja` by default, but users can still enable it with `DS_ENABLE_NINJA=1` until we can further debug to understand the problem.


Deepspeed have too many ops now, and it take too many time to pre-build all ops.
I notice deepspeed disabled
ninja4 years ago (#298) and I think we should consider enable it now.The issue mentioned in #298 can be solved by resolving
include_dirsto absolute path.