[FEA]: Does cutile-python have plans to integrate NCCL as the communication backend?
Open
Nobody has claimed this yet.
feature request
status: in-progress
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 155
- PR merge metrics
- No merged PRs in 30d
Description
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request?
High
Please provide a clear description of problem this feature solves
Integrating NCCL with CuTile-Python enables compute-communication operator fusion.
Feature Description
Are there plans to integrate NCCL as the communication backend? Thx.
Describe your ideal solution
def allgather_gemm():
nccl_device.allgather()
gemm()
Describe any alternatives you have considered
No response
Additional context
No response
Contributing Guidelines
- I agree to follow cuTile Python's contributing guidelines
- I have searched the open feature requests and have found no duplicates for this feature request
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
The issue names no files, tests, or entry points. Start by locating cuTile-Python's communication or device backend abstractions and existing collective-operation support, then determine whether NCCL integration fits the project architecture. Done would mean a decided implementation scope for NCCL-backed communication and a validated path for the allgather-plus-GEMM example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100