microsoft / microsoft/ntttcp-for-linux
100% CPU utilization while bandwidth limit configured with low rate 100-1000 Mbit/s
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 426
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
ntttcp v1.4
While running ntttcp client with limit 100-1000 mbit/s getting 100% CPU utilization, removing "-B" flag or specifying high bandwidth like 10 Gbit/s resolves the issue
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 reproducing the ntttcp v1.4 client case with the "-B" bandwidth limit at 100–1000 Mbit/s. Compare it with runs without "-B" and at 10 Gbit/s; done means the configured low-rate limit no longer causes 100% CPU utilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100