pytorch / pytorch/gloo

Non-blocking collectives

Open
#321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.5k
Forks
368
Avg merge
19h 32m
Merged PRs (30d)
3

Description

Hi all,
I was going through gloo and I couldn't find any non-blocking collective operations. Is there a way to achieve non-blocking operations ATM? or are there any plans for the future?

Contributor guide

Open the contributing guide

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 reviewing Gloo's existing collective operation APIs and documentation to determine whether non-blocking variants already exist. The issue names no files or tests; completion would require establishing the intended non-blocking API and implementation scope, or documenting the current support and future plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.