Does SimCCl support alltoall？
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 184
- Avg merge
- 13h 4m
- Merged PRs (30d)
- 1
Description
I implement alltoall like nccl-tests does：
NCCLCHECK(ncclGroupStart());
for (int r=0; r<nDev; r++) {
NCCLCHECK(ncclSend(&mock_outp, size, ncclFloat, r, comms[r], NULL));
NCCLCHECK(ncclRecv(&mock_outp, size, ncclFloat, r, comms[r], NULL));
}
NCCLCHECK(ncclGroupEnd());
But SimCCl does not print run time
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 tracing SimCCl's handling of the ncclGroupStart, ncclSend, and ncclRecv sequence shown in the issue, and compare it with the nccl-tests alltoall pattern. Check how SimCCl reports runtime for this operation. Done means the equivalent alltoall run produces a runtime measurement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100