Project

General

Profile

Actions

action #110470

closed

X-Forwarding via SSH is very slow on ppc64le

Added by rainerkoenig about 2 years ago. Updated 11 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2022-04-29
Due date:
% Done:

0%

Estimated time:

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.


Related issues 1 (0 open1 closed)

Related to qe-yam - action #120852: Move ssh-X@ppc64le-hmc-single-disk to YaST development job groupResolvedtinawang1232022-11-22

Actions
Actions #1

Updated by rainerkoenig about 2 years ago

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.

Actions #2

Updated by JERiveraMoya about 2 years ago

  • Status changed from In Progress to Blocked
  • Target version set to Current
Actions #3

Updated by openqa_review about 2 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #4

Updated by JERiveraMoya almost 2 years ago

  • 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.

Actions #5

Updated by JERiveraMoya over 1 year ago

  • Target version changed from Current to future
Actions #6

Updated by JERiveraMoya over 1 year ago

  • Target version deleted (future)
Actions #7

Updated by openqa_review over 1 year ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #8

Updated by JERiveraMoya over 1 year ago

  • Related to action #120852: Move ssh-X@ppc64le-hmc-single-disk to YaST development job group added
Actions #9

Updated by openqa_review over 1 year ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #10

Updated by JERiveraMoya 11 months ago

  • 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.

Actions

Also available in: Atom PDF