TimelyDataflow / TimelyDataflow/timely-dataflow
Disable asynchronous message transfer?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
Hi, I am new to Timely Dataflow
I am so impressed by the design philosophy of Timely Dataflow.
Currently, I am investigating the performance impact of its asynchronous execution engine on
for some BSP-based algorithms such as PageRank.
Is there any way for me to disable 'asynchronous booster' in the system so that I can check the performance benefit of it?
Thanks!
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. Start by locating the asynchronous execution engine and its configuration in the Rust code, then check how BSP-based execution is selected or controlled. Done means establishing whether asynchronous transfer can be disabled and identifying the required implementation or documentation scope.
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
- 25/100