TimelyDataflow / TimelyDataflow/timely-dataflow
Research Question For Highly Concurrent Systems
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
Hello, I am a PhD student at the University Of Pennsylvania. I'm currently leading a research project on decreasing nondeterminism in highly concurrent systems which communicate mostly via channels.
Our ongoing work has applied our approach to Servo (abstract here)
I think timely-dataflow may be a good case study for our research project. In Servo we mostly focused on lowering the number of intermittent test failures. My main question is: Is nondeterminism ever a problem for timely-dataflow? Does it affect debuggability, reproducibility, development, or any other nice-to-have properties of the system?
Thank you for your time.
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
No file, test, or entry point is named. Start by determining whether nondeterminism is observable in timely-dataflow and how it affects debuggability or reproducibility; the issue is complete only when the research question has a documented, project-relevant conclusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100