-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[BUG] Invalidate trace cache warning #6985
Comments
Same |
Yejing-Lai
pushed a commit
to Yejing-Lai/DeepSpeed
that referenced
this issue
Feb 24, 2025
Make trace cache warnings configurable, and disabled by default. Fix deepspeedai#6985, deepspeedai#4081, deepspeedai#5033, deepspeedai#5006, deepspeedai#5662 --------- Signed-off-by: Olatunji Ruwase <[email protected]>
gyou2021
pushed a commit
to gyou2021/DeepSpeed
that referenced
this issue
Feb 28, 2025
Make trace cache warnings configurable, and disabled by default. Fix deepspeedai#6985, deepspeedai#4081, deepspeedai#5033, deepspeedai#5006, deepspeedai#5662 --------- Signed-off-by: Olatunji Ruwase <[email protected]> Signed-off-by: gyou2021 <[email protected]>
tohtana
pushed a commit
that referenced
this issue
Feb 28, 2025
Make trace cache warnings configurable, and disabled by default. Fix #6985, #4081, #5033, #5006, #5662 --------- Signed-off-by: Olatunji Ruwase <[email protected]> Signed-off-by: Masahiro Tanaka <[email protected]>
ys950902
pushed a commit
to ys950902/DeepSpeed
that referenced
this issue
Mar 6, 2025
Make trace cache warnings configurable, and disabled by default. Fix deepspeedai#6985, deepspeedai#4081, deepspeedai#5033, deepspeedai#5006, deepspeedai#5662 --------- Signed-off-by: Olatunji Ruwase <[email protected]> Signed-off-by: yisheng <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
During training I receive the following warning multiple times per epoch:
Invalidate trace cache @ step 1 and module 1: cache has only 1 modules
This is a bit of an odd message, I have done some digging, and these trace warnings seem to be a common issue people report here, but none like this one. Is there any input from the developers about what could be at the root of it? I spent quite some time figuring it out, but couldn't rely figure it out. Any help would be appreciated!
Also it would be really nice if there is an option to suppress this warning, in case it's not relevant. The way it's coded this is quite difficult.
ds_report output
The text was updated successfully, but these errors were encountered: