IPython creates too many round trips

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the controller, client, and engine message flow described in the issue, focusing on how one command becomes one message per engine. There are no files or tests named, so first locate those communication entry points and establish a reproducible large-data case. Done should mean fewer redundant round trips and evidence that large pushes no longer traverse the single controller-client channel once per engine.

Written by the indexing model from the issue text.

Description

enhancement

Surprisingly, IPython sends one message per engine per command between the controller and the client. The controller then routes each one of these messages to the appropriate engine.

This has a potential to be a large bottelneck, for example if you want to push a large piece of data to the engines. It will be copied N times and push through the single channel between the controller and client.

Dominant language
Python
Stars
5
Forks
1
No merged PRs in 30d

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.

More from enthought/distarray

All issues in enthought/distarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.