Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

print to windows terminal as slow as conhost, git-bash.exe 10x faster #9187

Closed
ta946 opened this issue Feb 16, 2021 · 2 comments
Closed

print to windows terminal as slow as conhost, git-bash.exe 10x faster #9187

ta946 opened this issue Feb 16, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ta946
Copy link

ta946 commented Feb 16, 2021

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.804]
Windows Terminal version (if applicable): 1.5.10411.0 & Preview 1.6.10412.0

Any other software?
git-bash (mintty 3.4.1 xterm)

Steps to reproduce

python -c "from timeit import default_timer as default_timer; thisTimer = default_timer(); list(print(i) for i in range(100000)); print('thisTimer', round(default_timer()-thisTimer,2))"

Expected behavior

Windows terminal mentions GPU accelerated text rendering so I was expecting a significant speed performance over conhost.

Actual behavior

running the above python script to print 100k lines takes 7s on conhost with no speed difference using windows terminal (powershell or cmd)
Running the same script with git-bash takes 0.7s but it seems to render the screen in segments as opposed to wt and conhost clearly showing each line bring printed.

Is there a setting or option to let windows terminal print to console faster even at the cost of readability as a common use case i have is executing a long running code with a large text dump per second but running it in conhost ends up slowing down my script

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 16, 2021
@zadjii-msft
Copy link
Member

I believe we're using #3075 to track the latest iteration of "Terminal not speed enough" (previously, #1064). The Terminal is actually a bit faster than conhost, but at the end of the day, there's actually still a conhost sitting between the Terminal and whatever the client application is. So that still slows things down a bit.

/dup #3075

@ghost
Copy link

ghost commented Feb 16, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Feb 16, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 16, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants