typelevel / typelevel/cats-effect
Decide if we want to keep `cedeBypass`
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
This was ported directly from Tokio, but it's not actually clear that it makes a different in practice. This optimization only applies when the local queue is empty, meaning that the runtime must be under extremely light load. In other words, it optimizes microbenchmarks rather than production systems. We should probably remove it, since it makes a number of invariants a bit shaky within the state machine.
With that said, we shouldn't do this until we get a proper systems benchmark harness in place.
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 locating the cedeBypass implementation and the state-machine invariants it affects. Review the proposed systems benchmark harness requirement before evaluating whether the optimization matters beyond microbenchmarks. Done means the benchmark evidence supports a clear decision and the runtime behavior and invariants are updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100