Try to remove mutex from PushPull input adapter
Open
Nobody has claimed this yet.
tag: internal
type: enhancement
- Dominant language
- Python
- Stars
- 441
- Forks
- 90
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 5
Description
Looks like when replaying a considerable amount of data, we hit a lot of contention and slowdown from this mutex which is locked/unlocked per tick when pushing data.
Would be good to see how we can do away with this mutex to speed up replay
Contributor guide
No contributing guide indexed for this repository
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 PushPull input adapter and tracing where its mutex is locked and unlocked for each tick. Profile considerable-data replays to confirm the contention, then define a synchronization approach that preserves correct pushing while reducing replay slowdown; done means the adapter remains correct and replay performance improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- performance, stream-processing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100