Cannot use more than 128 parallel streams
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- cli, networking
Research direction
Start by locating the C code that parses or validates the -P parallel-stream option and identify where the value 128 is enforced. Update the supported maximum to 256, then verify that values through -P 256 are accepted and that the existing limit behavior remains covered by the project's tests.
Written by the indexing model from the issue text.
Description
I have a use case that calls for generating more than 128 streams of traffic, currently it appears values beyond -P 128 are not supported.
Is there any reason why this can't be increased? Would you be open to a PR that bumps this to say 256?
- Dominant language
- C
- Stars
- 8.9k
- Forks
- 1.5k
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from esnet/iperf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
esnet/iperf#2101 · 2 comments ·
Maintainers usually reply within 2 days
-
Build failure on platforms without `<stdatomic.h>` due to use of non-standard `u_int64_t`Possibly taken @lgoettgens claimed this 114 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
esnet/iperf#2060 · 1 comment ·
Maintainers usually reply within 2 days
-
JSON output (-J) emits two top-level "error" keys on server-relayed errorsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
esnet/iperf#2051 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
esnet/iperf#2086 · 10 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
esnet/iperf#2076 · 4 comments ·
Maintainers usually reply within 2 days
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
containers/bubblewrap#826 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Revivedx/SavageWindRecomp#488 ·
Maintainers usually reply within 1 day
-
needs-device
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
feature/themes QA/No release-notes/exclude tests tests/missing-coverage tests/test-quality
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
brave/brave-browser#60971 ·
Maintainers usually reply within 1 day