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

Naming issue about profile reports #94

Open
FindHao opened this issue Dec 3, 2024 · 1 comment
Open

Naming issue about profile reports #94

FindHao opened this issue Dec 3, 2024 · 1 comment

Comments

@FindHao
Copy link
Member

FindHao commented Dec 3, 2024

tritonbench export
kineto traces to /tmp/tritonbench/<operator>/<debug_type>/<name>_<input>/<hostname>_<id>.pt.trace.json ,
ncu reports to /tmp/tritonbench/<operator>/<debug_type>/<name>_<input>/ncu_output.ncu-rep, and nsys reports to /tmp/tritonbench/<operator>/<debug_type>/<name>_<input>/nsys_output.nsys-rep. Because the report file names don't have any useful information, it is hard to identify different tests when we compare multiple reports.

Q1: Can we change the names with more information? Will this interrupt many places in testing?

Q2: Those reports locate at different folders for a single test, can we collapse the path structure like /tmp/tritonbench/<operator>/debug_type_name_input_nsys_output.nsys-rep? and add mode(fwd,bwd,fwd_bwd) etc.?

Q3: Can we add username into the path? like /tmp/tritonbench/user or /tmp/tritonbench_user like torchinductor? This can help for multi-users servers' testing.

@xuzhao9

@xuzhao9
Copy link
Contributor

xuzhao9 commented Dec 3, 2024

Sure, all the changes make sense to me. We can add helper functions in path_utils.py to manage the output paths.

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