Ntttcp stalling with `-P 200`

Open
#99 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c, python
Domain
networking, performance, testing

Research direction

Reproduce the stall with the receiver and sender commands in the issue, then run pytest test/functional_test.py -s. Start in src/ntttcp and trace the post-test cleanup path for 200 threads. Done means the -P 200 scenario completes cleanup without hanging and the functional test passes.

Written by the indexing model from the issue text.

Description

Overview

Ntttcp tool gets stuck in post-test cleanup in when 200(-P 200) threads are specified.

Repro

Run the following commands from receiver and sender
Receiver

./src/ntttcp -D -r -m 200,*,127.0.0.1 -D -t 5

Sender

./src/ntttcp -s127.0.0.1 -P 200 -t 5`

Shorthand

pip install pytest && pytest test/functional_test.py -s
Dominant language
C
Stars
426
Forks
108
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ntttcp-for-linux

All issues in microsoft/ntttcp-for-linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.