maybe_mark_step() — pytorch Function Reference
Architecture documentation for the maybe_mark_step() function in common.py from the pytorch codebase.
Entity Profile
Dependency Diagram
graph TD cea445e5_003e_b07a_0de9_43b0801fe53a["maybe_mark_step()"] f5d4c5a3_21f5_4ed1_f582_7d73c454a4d7["latency_experiment()"] f5d4c5a3_21f5_4ed1_f582_7d73c454a4d7 -->|calls| cea445e5_003e_b07a_0de9_43b0801fe53a 04a3a4a6_8db3_854d_a893_02c9542bf9dd["speedup_experiment()"] 04a3a4a6_8db3_854d_a893_02c9542bf9dd -->|calls| cea445e5_003e_b07a_0de9_43b0801fe53a style cea445e5_003e_b07a_0de9_43b0801fe53a fill:#6366f1,stroke:#818cf8,color:#fff
Relationship Graph
Source Code
benchmarks/dynamo/common.py lines 890–892
def maybe_mark_step(args):
if args.trace_on_xla:
xm.mark_step()
Domain
Subdomains
Called By
Source
Frequently Asked Questions
What does maybe_mark_step() do?
maybe_mark_step() is a function in the pytorch codebase.
What calls maybe_mark_step()?
maybe_mark_step() is called by 2 function(s): latency_experiment, speedup_experiment.
Analyze Your Own Codebase
Get architecture documentation, dependency graphs, and domain analysis for your codebase in minutes.
Try Supermodel Free