13 experiment framework benchmark harness#14
Open
leandrumartin wants to merge 14 commits intomasterfrom
Open
Conversation
Collaborator
Author
|
I've also now added a CSV with the experiment framework. I based the values off the "Scaling iperf3 to 200 Gbps: A Study in Network Tool Scalability" paper you had shared in Slack to try to get values that made sense and were reasonable, but I'm not sure whether they really make sense and are what we're looking for. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PLEASE NOTE the following text from the iperf3 license. Submitting a
pull request to the iperf3 repository constitutes "[making]
Enhancements available...publicly":
The complete iperf3 license is available in the
LICENSEfile in thetop directory of the iperf3 source tree.
Version of iperf3 (or development branch, such as
masteror3.1-STABLE) to which this pull request applies:Issues fixed (if any):
Brief description of code changes (suitable for use as a commit message):
Python files were added to run the client application with JSON output logged to a specific file. The Dockerfile was also updated to make clear that the user should expose both TCP and UDP ports (see paragraph below for command to run Docker image).
Running the image with
docker run -dp 5201:5201/tcp -dp 5201:5201/udp <image-name>(with the-dpoptions exposing both TCP and UDP; without this, UDP may be blocked) lets the user run the Python files and successfully generate output.