Added named_scope for WAN 2.1 Xprof profiling #285
+133
−66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added Name Scopes for WAN 2.1 XProf TraceView
Added
jax.named_scopefor the following componenets in WAN 2.1 DiT when theenable_jax_named_scopesflag is set as True (default as False). Run scripts:Log with enable_jax_named_scopes=True, XProf
Log with enable_jax_named_scopes=False, XProf
Below are the added named scopes:
So that we can have better observability for XProf TraceView (example XProf):

Comparing to the old one (example XProf):

Testing
Function
f5f212f2d15cf55de5b4007b180da00f91a746d2): row 176 to row 184 in the benchmark doc.(DP, FSDP, TP)=(2, 8, 1):I check the first DiT block to make sure the XLA Ops are exactly the same. So our new named scopes are not breaking fusions.