microsoft / microsoft/ntttcp-for-linux
Send throughput not actually testable
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 426
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
The windows version of ntttcp has the ability for a single sender to send to multiple receivers which does not work with this version of the utility. This served to essentially eliminate the receiver sides as bottlenecks allowing the client's send throughput to be fully measured. The windows syntax looked something like this: sender "ntttcp -s -t 60 -m 8,*,192.168.0.2 8,*,192.168.0.3 -l 256k -a 2 -p 5000"; receiver 1 "ntttcp -r -t 60 -m 8,*,192.168.0.2 -a 16 -p 5000"; receiver 2 "ntttcp -r -t 60 -m 8,*,192.168.0.3 -a 16 -p 5008".
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
No files, tests, or entry points are named. Start by tracing how sender and receiver arguments are parsed and how connection mappings are created, then compare them with the Windows multi-receiver syntax in the issue. Done means one sender can measure throughput while sending to multiple receivers without the receivers becoming bottlenecks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100