mlcommons / mlcommons/inference
Report Total Number of Accelerators for multi-host submissions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 650
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 6
Description
During the submission process, the summary CSV that is generated from the https://github.com/mlcommons/inference/blob/master/tools/submission/generate_final_report.py script reports Nodes and a#, where Nodes comes from number_of_nodes field (https://github.com/mlcommons/inference/blob/master/tools/submission/generate_final_report.py#L35) and a# comes from the accelerators_per_node field (https://github.com/mlcommons/inference/blob/master/tools/submission/generate_final_report.py#L38).
The intent of the summary script is to show the total number of accelerators. The current logic is fine with single-node submissions, but can be confusing from multi-node submissions. For example, a submission that uses 4 VMs/Nodes, each with 4 accelerator chips, will report Nodes as 4 and a# as 4, which is not wrong, but confusing. There should be somewhere reference of 16.
Suggestion: We can have another column with total_a to , or rename a# to report 16 accelerators total, where the script calculates 16 by multiplying number_of_nodes * accelerators_per_node.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tools/submission/generate_final_report.py, especially the logic around lines 35-38 that reads number_of_nodes and accelerators_per_node. Run the summary report generation on a multi-node submission and verify that the CSV makes the total accelerator count explicit, including the four-node, four-accelerator example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100