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

Closed
opened 2026-01-31 03:20:25 +00:00 by claunia · 2 comments
Owner

Originally created by @ta946 on GitHub (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

Originally created by @ta946 on GitHub (Feb 16, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none 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 <!-- A description of how to trigger this bug. --> 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 <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows terminal mentions GPU accelerated text rendering so I was expecting a significant speed performance over conhost. # Actual behavior <!-- What's actually happening? --> 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
claunia added the Resolution-Duplicate label 2026-01-31 03:20:25 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Feb 16, 2021):

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

@zadjii-msft commented on GitHub (Feb 16, 2021): 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
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12619