haskell-distributed / haskell-distributed/distributed-process
[DP-76] local inter-process communication doesn't need to go via the NC channel
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
[Imported from JIRA, posted by @hyperthunk Tim Watson at 26/Apr/13 7:16 PM as DP-76]
Some initial investigation suggests that this doesn't have much effect on message passing efficiency though. I'm not totally surprised, and I suspect any micro-benchmarks we come up with will vary considerably between applications. Hmph.
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; begin by locating the local inter-process messaging path and its NC-channel handling. Done would require an agreed implementation and evidence that local communication bypasses the NC channel without harming message-passing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100