yagna
yagna copied to clipboard
Merge `hybrid_performance` into `hybrid_ya_perf` checker and deploy it
We faced a few issues when runnin hybrid_performance
checker. Those issues are listed below.
Issues with hybrid_performance
checker:
- checker does not run according to the schedule,
- no results in
/tmp/test_result_hybrid_performance
, - requestor does not pay for running task
as this is overhead to maintain two checkers we decided to merge 'hybrid_performanceinto
hybrid_ya_perf` checker
As discussed (What should be done):
- merge
hybrid_performance
intohybrid_ya_perf
checker - add comments to
run.sh
scripts in ya_perf checker to highlight why particular part of the sccript is triggered ➔ ya-perf checker for performance measurements, performance checker for stress tests - scope of the scripts:
- ya_perf part of the script:
- 10 various nodes, transfer file for GFTP equal to 50MB, 10 pings:
- GFTP transfer test
- VPN ping
- VPN transfer test using
iperf3
(which ya_perf tool use by default)
- 10 fixed nodes, transfer file for GFTP equal to 50MB, 10 pings:
- GFTP transfer test
- VPN ping
- VPN transfer test using
iperf3
(which ya_perf tool use by default)
- 10 various nodes, transfer file for GFTP equal to 50MB, 10 pings:
- performance part of the script:
- 50 various nodes:
- VPN transfer test using
scp
with 10MB transfer file size (setup ya_perf tool accordingly)
- VPN transfer test using
- 50 various nodes:
- ya_perf part of the script:
- inform Devops about significant increase of tasks run time (as alerts may appear too often if Grafana is not adjusted respectively)
- when merge is done, deploy changed checker and observe for possible issues