TPReplay: timeout for multiple threads
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 8
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 3
Description
auto earliest_timestamp_time = std::chrono::steady_clock::now() + std::chrono::milliseconds(100);
TPReplay currently has a small (hardcoded) delay (100ms) at the start stage that allows for multiple outputs to stream in sync. This needs testing for high level of sources (or potentially making configurable).
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 at TPReplay's start stage and inspect the hardcoded 100 ms steady_clock delay shown in the issue. Test multiple outputs with a high number of sources to determine whether the timeout remains sufficient; define done as synchronized streaming behavior, or a clearly specified configurable timeout if that is chosen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100