Skip to content
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

No RANK specified in the TRACE FILE #974

Open
Ilex00para opened this issue Aug 8, 2024 · 1 comment
Open

No RANK specified in the TRACE FILE #974

Ilex00para opened this issue Aug 8, 2024 · 1 comment

Comments

@Ilex00para
Copy link

I tried to use the hta.trace_analysis.TraceAnalysis with trace files (json) create by the PyTorch profiler as recommended in the documentation.

with torch.profiler.profile( schedule=torch.profiler.schedule(wait=1, warmup=1, active=3, repeat=1), #schedule the profiler to start after 1 step, warmup for 1 step, run for 3 steps and repeat 1 time on_trace_ready= torch.profiler.tensorboard_trace_handler('./log/resnet18'), #save the trace to tensorboard by using a tracer object record_shapes=True, with_flops=True, with_module_call_stack=True, profile_memory=True, with_stack=True ) as prof:

I get the error that no rank is specified in the trace file, I dont use distributed processes:

2024-08-08 14:03:38,854 - hta - trace_file.py:L61 - ERROR - If the trace file does not have the rank specified in it, then add the following snippet key to the json files to use HTA; "distributedInfo": {"rank": 0}. If there are multiple traces files, then each file should have a unique rank value. 2024-08-08 14:03:38,855 - hta - trace_file.py:L92 - WARNING - There is no item in the rank to trace file map. 2024-08-08 14:03:38,855 - hta - trace.py:L535 - INFO - ranks=[] 2024-08-08 14:03:38,856 - hta - trace.py:L541 - ERROR - The list of ranks to be parsed is empty.

What could be the problem? I saw that you work on the support for tracing distributed workloads is it related to this?

@sraikund16
Copy link
Contributor

sraikund16 commented Sep 4, 2024

What type of workload were you running? If it was PT2 then it may have been caused by a profiling bug caused by pytorch/pytorch#134893. Please pull latest and try again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants