SSH Xstart sessions slowww [3]

SSH Xstart sessions slowww

Tuesday, March 27, 2012 9:25 PM - Jared

I am attempting to run an image manipulation program that deals with fairly high res images over xstart. Unfortunately the redraw rate makes it unbearably slow and painful to use.

I have tried using a full XDMCP session and it all works perfectly.

I have attempted the pseudo terminal allocation trick mentioned in another thread, as well as the compression option. Both to no avail.

Does anyone have any ideas on how I can speed up the Xstart sessions?

I am using xmanager 4 to connect to an ubuntu 10.04 server running xdm.

Program Ver. : Xmanager 4
Connect Method : Xstart connection


Re: SSH Xstart sessions slowww

Tuesday, March 27, 2012 10:57 PM - Support

This might has to with the SSH encryption. SSH encrypts all data transferred between computers and this may take more time compared to XDMCP.

Could you try running the application with Telnet and see if that makes any difference? Please be aware that Telnet is not a secure protocol.

Also, could you tell us the following information?

1. What is the name and version of the software?
2. What is the name and version of the remote host?
3. What is the size of the image file?

---
Technical Support


Re: SSH Xstart sessions slowww

Sunday, April 29, 2012 3:46 PM - Jared

Hi, I have tried using the TELNET protocol and all works OK, although extremely unreliable with constant freezing and unresponsive windows.

1. What is the name and version of the software?
- The software is developed in house.
2. What is the name and version of the remote host?
- Ubuntu 10.04
3. What is the size of the image file?
- Roughly 15mb


Re: SSH Xstart sessions slowww

Wednesday, May 2, 2012 5:08 PM - Support

Depending on how the in house software is programmed, it may require full 15mb to show the image.
SSH is almost always slower because it takes much longer to encrypt large binary data as oppose to just encrypting text.
Please use TELNET and see when the program freezes and fix that problem. You may have to work with in house developer to fix this issue.

Another possible solution is to use xvnc. To use xvnc, first, install vncserver and vncviewer on the remote host. Then:

1. Run vncserver with the following command: vncserver :13 (this will run vncserver on remote display number 13)
2. Open in house program on localhost:13
3. Open remote vncviewer by using the following command vncviewer localhost:13

---
Technical Support


Previous views: 129