microsoft / microsoft/superbenchmark
NVBandwidth benchmark results parsing bug
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 393
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
What's the issue, what's expected?:
When parse the results of NVBandwidth, there exist bugs in metrics name such as nvbandwidth/_sum_None. and nvbandwidth/device_to_device_latency_sm_sum_None
How to reproduce it?:
Log message or shapshot?:
Additional information:
Contributor guide
No contributing guide indexed for this repository
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 by locating the NVBandwidth result-parsing entry point and search for how metric names are assembled. Use the malformed names in the issue as reproduction targets, then verify that parsed results no longer include the reported _None suffixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100