action #110470
closed
X-Forwarding via SSH is very slow on ppc64le
Added by rainerkoenig about 2 years ago.
Updated 10 months ago.
Description
Motivation¶
ssh-x videomode in the ssh-X teststuite is extremely slow on ppc64le, leading to "noise" that can only be avoided by wait_still_screen calls.
We therefore created a Service Request to see if performance can be imprvoved.
This ticket is to collect all data and progress regarding X forwarding on ppc64le.
Status Update 2022-05-12¶
Measured now the speed between openqa.suse.de and redcurrant-12.qa.suse.de. 10 rounds with 69MB payload.
Average speed from openqa → redcurrant-12 is 33 MBytes/s.
Average speed from redcurrant-12 → openqa is 2388,8 KBytes/s
That mean in average the transfer from openqa to redcurrent-12 is 144 times faster than the other way round.
tracepath also shows, that there are no different routes between the 2 machines, depending on who is sender and receiver.
- Status changed from In Progress to Blocked
- Target version set to Current
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ssh-X@ppc64le-hmc-single-disk
https://openqa.suse.de/tests/8752115#step/accept_license/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Tags set to YaST
- Status changed from Blocked to New
- Assignee deleted (
rainerkoenig)
- Priority changed from Normal to Low
Moved to Backlog, to check in the near future.
- Target version changed from Current to future
- Target version deleted (
future)
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ssh-X@ppc64le-hmc-single-disk
https://openqa.suse.de/tests/9776223#step/accept_license/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Related to action #120852: Move ssh-X@ppc64le-hmc-single-disk to YaST development job group added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ssh-X
https://openqa.suse.de/tests/9969416#step/accept_license/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Tags deleted (
YaST)
- Status changed from New to Rejected
Seems that for some reason the scenario is not scheduled anymore in development so we lost track of failures, but anyway we should not focus much in problems with power kvm, as it is unsupported.
Also available in: Atom
PDF