haskell-distributed / haskell-distributed/distributed-process

[DP-72] use a per-vnode shared buffer to serialize small messages

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

Nobody has claimed this yet.

enhancement
Dominant language
Haskell
Stars
751
Forks
99
Avg merge
45m
Merged PRs (30d)
2

Description

[Imported from JIRA. Reported by Tim Watson [Administrator] @hyperthunk) as DP-72 on 2013-03-28 16:59:56]
As (another) optimisation, we could take advantage of recent improvements to the binary package that allow us to pre-allocate a buffer and re-use it for serializing small messages.

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

The issue provides no files, tests, or entry points. Start by locating vnode message serialization and the binary package usage, then determine how a per-vnode buffer could be reused safely for small messages. Done should include the optimization and evidence that serialization remains correct.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.