haskell-distributed / haskell-distributed/distributed-process
[DP-71] Can we avoid using System.Timeout to handle timeouts
Nobody has claimed this yet.
- 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-71 on 2013-03-11 16:22:25]
As per https://github.com/snoyberg/posa-chapter/blob/master/warp.md#performance-of-warp, the built in timeout functionality is quite expensive (requiring an additional user thread). Is it possible we might garner something from their timeout-manager implementation and do something similar for CH?
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
Start by reading the linked Warp performance discussion and the System.Timeout usage in distributed-process. Compare the proposed timeout-manager approach with the current timeout behavior and identify the affected Cloud Haskell components. Done requires an agreed design and evidence that it avoids the stated thread and performance costs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100