FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Shared-memory via ray.put()/ray.get() vs socket IPC for data transfer · Issue #71 · TransferQueue/TransferQueue · GitHub

This repository was archived by the owner on Jan 21, 2026. It is now read-only.
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Shared-memory via ray.put()/ray.get() vs socket IPC for data transfer #71

Description

Hi team,

Thanks for developing TransferQueue — I’m working on a multi-process inference system and your framework is very relevant.

Quick question: In your architecture, have you compared using the Ray object store (ray.put() / ray.get() for shared memory IPC) versus socket/IPC (or storage + metadata) transport for moving large tensor data between processes (same node or across nodes)?

  • Do you have benchmark data or evidence showing one approach is better than the other in your usage scenario?
  • Which mechanism does TransferQueue currently assume or recommend (shared-memory via Ray, or socket/IPC)?
  • If I’m building a system that transfers large batches across worker processes, would you recommend starting with Ray’s object store or custom IPC/sockets, given complexity vs performance trade-offs?

Thanks for your advice!
Best,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL