I agree, someone who works with me on xterm.js focuses hard on throughput so i know there's a lot you can squeeze out there (though we need to deal with JS which has another set of problems).
-
-
Replying to @Tyriar @cmuratori and
Realistically though the 10x from fastpipe wouldn't be able to be entirely eliminated as I understand it's a fairly complex problem. Additionally it's critical to backwards compatibility of Windows console apps so it has to do things sometimes like rerender the whole screen.
2 replies 0 retweets 0 likes -
But those aren't really very justifications in my opinion. Just put a button in your config that is "no backwards compat", and if you check that, then your terminal runs really fast :)
2 replies 0 retweets 2 likes -
Replying to @cmuratori @Tyriar and
But more specifically, I'm pretty sure even back-compat parsing could probably be done an order of magnitude faster than it's being done now. I can't say for sure but I strongly suspect that code is not high-perf code, if one were to go look.
2 replies 0 retweets 3 likes -
Replying to @cmuratori @Tyriar and
Just want to say, the ConPTY slowness has been largely improved in the last several years. But sadly that’s only available in the latest Windows version (insider preview). The Windows Terminal slowness is a thing, and people are working on it.
1 reply 0 retweets 3 likes -
Replying to @ChesterLiu2 @cmuratori and
Good to hear, but I'll believe it when I see it
@code's terminal unfortunately slows to a crawl only on Windows4 replies 0 retweets 0 likes -
Replying to @Tyriar @ChesterLiu2 and
I wonder if it'd make sense to ship the latest conhost/OpenConsole from the WT repo with code? Not sure if there are some stability issues with doing that
2 replies 0 retweets 0 likes -
Replying to @nikc_12 @ChesterLiu2 and
I'm sure it's possible, but that's instability I wouldn't really want to take on plus that would open us to getting our build broken by another team.
2 replies 0 retweets 2 likes -
Replying to @Tyriar @cmuratori and
What
@Tyriar trying to say in previous comment, i think, is that refterm lacks the entire layer of handling legacy Win32 console apps, which includes actually a large portion of apps, including vim and far. Both conhost and WT does not have the luxury.1 reply 0 retweets 1 like -
Replying to @ChesterLiu2 @Tyriar and
That is false, as I demonstrated in the actual demo. The non-fast-pipe version, which was 10x faster than Windows terminal, _was going through conhost_.
1 reply 0 retweets 4 likes
And separately, this is what I mean when I say it gets tiresome dealing with all of these nonsense excuses. People just say things on Twitter even though there was literally a demo _they could watch_ proving the thing that they said was false.
-
-
Replying to @cmuratori @ChesterLiu2 and
So just to recap, if somehow watching the video was too difficult: _with_ backwards compat conhost, refterm is 10x faster than Windows terminal. If you _bypass_ that as a speed test, you get _another_ 10x faster, for a total of 100x. I explained this as clearly as I could.
1 reply 0 retweets 4 likes -
Replying to @cmuratori @ChesterLiu2 and
That is why I took great pains throughout the video to show the performance with _both_ fast_pipe.h and without, so you could see where each slowdown was.
1 reply 0 retweets 2 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.