SSH Delay while typing

Hello,

Do you happen to have the same delay when accessing the same terminal outside of Remote Desktop Manager?

Best regards,

No, I use putty .. it's typing fast but when I use the same server in Remote Desktop Manager there is a delay when I type the commands on it.

Hello,

Thank you for your response.

Could you kindly ensure that you are using the latest version of RDM?

In the meantime, could you let me know the details of your datasource? Additionally, would it be possible for you to export the entry and send it to me via email? I’ve sent you a secure link by email for you to upload the entry.

Once I receive it, I will test it on my end.

Looking forward to your response.

Best regards,

You can check this link,
https://drive.google.com/file/d/1pnEzAjs5vaNVu_ok7_Ip29Rohk-24Tjy/view?usp=sharing
Note when watch video change quality to 1080p to see it clearly.

I uploaded a video in which I compared between RDM and Putty for the same server, you will see a delay when I try to type commands.
When i type commands on Putty, you will see it's fast and smoothly.

Note, I use the latest version from RDM.

Hi,

You can check the "Disable Nagle's algorithm" on the "Advanced" tab. This could help in this case.

I will also investigate this, but the multi-platform nature of RDM adds some hurdles to performance that a Windows app like Putty does not have.

Regards

Thanks, I checked this option "Disable Nagle's algorithm" but still delay exists.
Is there any option or tuning I can do to enhance this delay?

Syntax highlighting can also impact performance. You can set "Syntax highlighting mode" (in the "Terminal" tab, "Display" sub-tab) to "Custom". This makes sure it is not using any global syntax highlighting. If it is already set to custom, the "Customize syntax highlighting" button will allow you to edit the syntax settings. It is possible to enable/disable each keyword without deleting them.

Otherwise, the delay could be related to graphics rendering. In that case, the delay would change dependent on the terminal window size.

I am also currently reworking the terminal. There are many small improvements that will be included that should impact performance. I expect those changes to be available in the 2025.2 version.

Regards

Hi, i have the same issue, any update on this? there an almost 1 sec delay when typing on the ssh console.
Local SSH (thru RDM too) having 1ms latency works fine, but when using a session that has about 70ms latency, it has a lot of delay on the console, that does not happen on putty.
Im on 2025.2.23.0

Hello,

Thank you for your response.

Could you please let me know when this issue started to occur? Has the delay been observed only with SSH sessions, or are other entry types also affected?

Additionally, could you confirm your data source?

Lastly, do you see any relevant information in the Profiler under the Help tab while typing into an SSH session?

Best regards,

i installed 2025.2.23.0 from scratch so it started then.
only ssh sessions.
dont see anything appear in the profiler.
the datasource is a local file.
the same ssh session but with a local ip address, does not delay.
it only delays when using an external (internet) ip address, in this case, today testing with one with 200ms latency, which is pretty much the perceived delay when typing, so its not processing the keystrokes locally, making it pretty unusable

Hello,

Thank you for your response.

I have created a case for further investigation and will be reaching out to request a recording shortly.

Best regards,

Hi,

I would like to know: when using putty, do you set it up to have local echo, or do you check some other options? Because it is normal procedure for a terminal to send a key stroke to the server and wait for the output from the server to display it. If the network between the terminal and the server has a long round trip time, then the delay is normal. I know putty does the same, but has options to handle those cases.

Regards

Hi,

I would like to know: when using putty, do you set it up to have local echo, or do you check some other options? Because it is normal procedure for a terminal to send a key stroke to the server and wait for the output from the server to display it. If the network between the terminal and the server has a long round trip time, then the delay is normal. I know putty does the same, but has options to handle those cases.

Regards

@Denis Vincent

its all default as it comes, havent changed the echo (if i enable it, i see duplicated keystrokes, i press a single time a, i get "aa" on the console).
Putty as default does not have this issue, putty works correctly.

There is also another issue altought its not about a delay, it prevents using certain stuff with this embed terminal.
If you open midnight commander (mc / apt-get install mc) and you click with the mouse on any part of the MC screen, you get on the terminal the text "4732;16;932;21;47" instead of clicking on the tab panel of MC. You also cant use shift+f4, it also sends weirds commands onto the console. Putty obviously works fine in this scenario too, so the console that RDM is using does not replicate putty, and it does not work correctly.

https://i.imgur.com/bisgvh5.png

@Ez
Thanks for the info, I will look into this as soon as I can. But since these are not problems I encountered in my tests (both the delay and the mouse click in mc), the solution might be hard to find.

Regards

@Ez
Thanks for the info, I will look into this as soon as I can. But since these are not problems I encountered in my tests (both the delay and the mouse click in mc), the solution might be hard to find.

Regards

@Denis Vincent
do you want me to set up a vm with a remote connection so you can check it and debug it there? if that helps you, otherwise as you say, without reproducing it yourself im not sure how much hope there is for this to be resolved soon and i will have to back to royalts :(

@Denis Vincent
do you want me to set up a vm with a remote connection so you can check it and debug it there? if that helps you, otherwise as you say, without reproducing it yourself im not sure how much hope there is for this to be resolved soon and i will have to back to royalts :(

@Ez
Yes, it would quite helpful. but I am a bit overloaded right now. So if the access to the VM would be limited in time, it would be best to wait until I am ready to use it.

okay, let me know when

Hi @Ez

I have found something that could cause delays, I have made the change and it will be available in our next release which should happen next week. If the problem persists, let me know and we'll arrange something to test with you VM.

Hi @Ez

I have found a bug that should fix your mouse problems in mc. It will be available in the next release or RDM (around next Tuesday).

As for the shift+F4 problem, you can change the "Function keys mode" setting in the "Keyboard" tab of the entry's properties. The most likely value for you should be "Xterm", but you can also try Linux, VT400 and VT100+.

Regards

Regarding the shift+f4 on midnight commander to create a file, xterm did the trick

Is it 2025.2.30.0 the version with the delay fix? if so, im still having the same issue

@Ez

For the delay, as well as for the mouse, the fix is in 2025.3.17.0 which is available but not as auto update. We're about to release 2025.3.18.0 which should be available as auto update.

does 2025.3.20 contains the same fix? im still having the issue with that version

@Ez
Yes, the same fix is available for .18 and higher.

That being said, I have found a strong potential for delays (and other problems that were reported). I am starting to work on a fix for that, It should be available on the next release, if not then on the next after that.

@Ez
I have made a fix for the delay. It will be part of the 2025.3.21 (or higher) release expected late this week or next week. I have strong confidence in this fix (though not a 100%), so let me know if it works or not.

Regards

was the fix included in 2025.3.21.0? if so, i still have the same issue

Yes, it is included. I am kind of surprised the issue still persists.
Have you tried changing, in the "Advanced" tab, the "Internet protocol" setting? Try either forcing it to IPv4 or IPv6 (I assume the host is specified by name and not an explicit IP address). I am wondering if RDM is not resolving through a different route than putty because of this.

May I know if linux 2025.3.2.3 fixed? I also encounter ssh input delay.

@chihangc

I haven't worked on input delay for a while, but I will make time to find a way to streamline the input pipeline since some users are still experiencing delays.

Regards