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

Allow users to choose iperf/iperf3 test via GUI (also choose traceroute options) #113

Closed
sowmyab opened this issue Mar 25, 2016 · 3 comments
Assignees
Milestone

Comments

@sowmyab
Copy link
Contributor

sowmyab commented Mar 25, 2016

A user reported

"......after the upgrade to v3.5.1, a single CPU in the LIVA box hits 99.9% CPU utilization when I run bwctl tests manually. When I force the bwctl test to use iperf instead of iperf3 (adding "-T iperf” option to bwctl command), the performance goes back to normal (~900Mbps), and both CPUs are utilized.

Is there a way to make the regular bandwidth tests to use iperf instead of iperf3 by default in perfSONAR v3.5.1?"

Currently, this is not possible via GUI and has to be done manually by editing the regulartesting.conf file. It will be valuable to add this option to GUI.

@apertome apertome added this to the 3.6 milestone Apr 4, 2016
@apertome
Copy link
Contributor

apertome commented May 6, 2016

This should go under the "advanced" tab.

@lisaens
Copy link
Contributor

lisaens commented Jun 14, 2016

I previously added a Tools selector to the advanced tab for throughput tests. It allows the user to add, remove, and drag to reorder iperf and iperf3.
Today, I moved the Tools selector for traceroute tests to the advanced tab and made it work like that for throughput tests. Users can choose and drag to reorder traceroute, tracepath, and paris-traceroute.

@lisaens lisaens changed the title Allow users to choose iperf/iperf3 test via GUI Allow users to choose iperf/iperf3 test via GUI (also choose traceroute options) Jun 17, 2016
@lisaens
Copy link
Contributor

lisaens commented Jun 17, 2016

This has been merged into master as part of the advanced-tab branch

@lisaens lisaens closed this as completed Jun 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants