Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add burst support #149

Merged
merged 1 commit into from
Jul 22, 2024
Merged

Add burst support #149

merged 1 commit into from
Jul 22, 2024

Conversation

venkataanil
Copy link
Contributor

@venkataanil venkataanil commented Jun 21, 2024

Netperf's TCP_RR supports burst mode which allows netperf process to send multiple transactions in flight at one time.

When run with just a single instance of netperf, increasing the burst size can determine the maximum number of transactions per second which can be serviced by a single process

Running burst with concurrent netperf tests is like “aggregate of aggregates” and helps in determine the maximum number of transactions per second on the node.

By default, TCP_RR uses burst mode of one transaction in flight at one time.

Burst mode is similar to queue depth in other testing tools.

Burst is added to results reporting to differentiate tests run with different burst configuration.

As "-m" is TCP_STREAM specific option, it is configured for STREAM testing only. "-r" option is used to specify packet size for netperf TCP_RR testing.

Type of change

  • Refactor
  • New feature
  • Bug fix
  • Optimization
  • Documentation Update

Description

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please describe the System Under Test.
  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Netperf's TCP_RR supports burst mode which allows netperf process
to send multiple transactions in flight at one time.

When run with just a single instance of netperf, increasing the
burst size can determine the maximum number of transactions per
second which can be serviced by a single process

Running burst with concurrent netperf tests is like
“aggregate of aggregates” and helps in determine the maximum
number of transactions per second on the node.

By default, TCP_RR uses burst mode of one transaction in flight
at one time.

Burst mode is similar to queue depth in other testing tools.

Burst is added to results reporting to differentiate tests
run with different burst configuration.

As "-m" is TCP_STREAM specific option, it is configured for
STREAM testing only. "-r" option is used to specify packet size
for netperf TCP_RR testing.

Signed-off-by: venkataanil <anil.venkata@enovance.com>
README.md Show resolved Hide resolved
Copy link
Collaborator

@vishnuchalla vishnuchalla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. And a very nice writeup too.

Copy link
Member

@rsevilla87 rsevilla87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@rsevilla87 rsevilla87 merged commit 6065e03 into cloud-bulldozer:main Jul 22, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants