Code-server terminal lag

[xqdoo00o]

I'm using the code-server 1.70.2 in wsl.

Sometimes the terminal lag after I type in command, I tried to debug in chrome, and find that if command no lag, the websocket shows upload binary message immediately. If command lag, after a few ms(up to 1s) the websocket shows the messages , and the terminal shows which I typed in at the same time.

I use code-server in local wsl, so the network factor could be excluded.
Would it help if put websocket code in webworker (Found this old bug)? or other code causeing this random terminal & websocket lag?

[connor4312]

I think to debug this we should make some "latency measurement" commands that would print diagnostic info that users could share...

[SuhasHebbar]

The now removed code-server serve-local works way better in this scenario for running code-server locally in WSL or a container.

I am guessing the latency is unavoidable since code tunnel is not P2P and directs all traffic through microsoft's tunnel servers despite running the server locally. VSCode's terminal tries to handle the lag by optimistically displaying keypresses before the server response but it doesn't help much and doesn't work very well with vim keybindings.

[connor4312]

In microsoft/vscode#182653 we now show the latency of slow connections

The request for serve-local is tracked in microsoft/vscode#168492