microsoft / microsoft/superbenchmark

[Suggestion] Separate benchmark keys for nccl without sharp and nccl with sharp

Open
#641 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
393
Forks
90
PR merge metrics
No merged PRs in 30d

Description

What would you like to be added:
saperate the benchmark keys for nccl without sharp and nccl with sharp

Why is this needed:
easier for sb result summary consumer to distinguish between values

Without this feature, how does current superbenchmark work
manual modify the key

Components that may involve changes:
superbench result summary, nccl-test

Brief description of your proposal if any:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the superbench result summary currently generates benchmark keys for nccl-test results. Identify where the sharp and non-sharp cases are represented, then make their keys distinct and verify that result summary consumers can distinguish both values without manual edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.