We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm running this: pscheduler task throughput --dest hostname --duration 30 --parallel 8 --fq-rate 12.5g
But I see this iperf3 client started: /usr/bin/iperf3 -p 5201 -c newy32aoa-ps-tp.es.net -t 30 --json -P 8 --rsa-public-key-path /var/pscheduler-server/runner/tmp/tmpipep100_/tmperwjg965/public-key --username McphfbPUwjZFhL1CGLeP
no "--fq-rate"
Also, per-stream tput varied from 10-15 to 15G; thats how I knew to too look for a problem.
The text was updated successfully, but these errors were encountered:
Looks like the modification to the plugin was incomplete. I'll get that fixed in the next release.
Sorry, something went wrong.
Add --fq-rate arg to iperf3 invocation. #1483
742f6fc
mfeit-internet2
No branches or pull requests
I'm running this:
pscheduler task throughput --dest hostname --duration 30 --parallel 8 --fq-rate 12.5g
But I see this iperf3 client started:
/usr/bin/iperf3 -p 5201 -c newy32aoa-ps-tp.es.net -t 30 --json -P 8 --rsa-public-key-path /var/pscheduler-server/runner/tmp/tmpipep100_/tmperwjg965/public-key --username McphfbPUwjZFhL1CGLeP
no "--fq-rate"
Also, per-stream tput varied from 10-15 to 15G; thats how I knew to too look for a problem.
The text was updated successfully, but these errors were encountered: