starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Noticeable lag / delay when using Remote Desktop #6704

New Issue
Closed
opened 2026-01-31 00:45:14 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 00:45:14 +00:00
Owner
Copy Link

Originally created by @Brand-Wylie on GitHub (Mar 2, 2020).

When I open Windows Terminal on Windows 10 in a Remote Desktop session there is noticeable input delay. Opening a separate PowerShell or CMD shell within the same environment performs normally.

Originally created by @Brand-Wylie on GitHub (Mar 2, 2020). When I open Windows Terminal on Windows 10 in a Remote Desktop session there is noticeable input delay. Opening a separate PowerShell or CMD shell within the same environment performs normally.
claunia added the Resolution-DuplicateProduct-TerminalArea-Performance labels 2026-01-31 00:45:14 +00:00
claunia commented 2026-01-31 00:45:15 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 3, 2020):

It's not just when using Remote Desktop. Even in a VM given max resources possible (without causing insufficient resources for base OS), it's slow opening, especially since my default is PS Core and that takes awhile to load PS profile (in addition to WT profile).

@WSLUser commented on GitHub (Mar 3, 2020): It's not just when using Remote Desktop. Even in a VM given max resources possible (without causing insufficient resources for base OS), it's slow opening, especially since my default is PS Core and that takes awhile to load PS profile (in addition to WT profile).
claunia commented 2026-01-31 00:45:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 3, 2020):

Total spitball: maybe this is due to the Remote Desktop / VM connection trying to virtualize the DX rendering?

I'm really not sure though, it's hard to differentiate this from just #1064. I'm inclined to just close this as a dupe without more specific data for this scenario. We would definitely need some perf traces on this scenario specifically to see what the hot paths are here.

@zadjii-msft commented on GitHub (Mar 3, 2020): Total spitball: maybe this is due to the Remote Desktop / VM connection trying to virtualize the DX rendering? I'm really not sure though, it's hard to differentiate this from just #1064. I'm inclined to just close this as a dupe without more specific data for this scenario. We would definitely need some perf traces on this scenario specifically to see what the hot paths are here.
claunia commented 2026-01-31 00:45:15 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 3, 2020):

maybe this is due to the Remote Desktop / VM connection trying to virtualize the DX rendering?

I think that's exactly what's happening. However, equally possible as a result of that is that it fails and then performs software rendering instead. Not sure if there's a way to boost speed of software rendering to test but if possible, I'd add some library to deal with boosting software rendering speed to the project if the code can't be rewritten well enough to gain noticeable perf gains.

@WSLUser commented on GitHub (Mar 3, 2020): >maybe this is due to the Remote Desktop / VM connection trying to virtualize the DX rendering? I think that's exactly what's happening. However, equally possible as a result of that is that it fails and then performs software rendering instead. Not sure if there's a way to boost speed of software rendering to test but if possible, I'd add some library to deal with boosting software rendering speed to the project if the code can't be rewritten well enough to gain noticeable perf gains.
claunia commented 2026-01-31 00:45:15 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 3, 2020):

Make this ticket (or the other) about adding Boost: https://github.com/boostorg/boost to the project.

@WSLUser commented on GitHub (Mar 3, 2020): Make this ticket (or the other) about adding Boost: https://github.com/boostorg/boost to the project.
claunia commented 2026-01-31 00:45:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 3, 2020):

I mean I'm not sure how just "adding Boost" to the terminal would be a magic bullet to get a perf gain out of the Terminal - we'd need actual logs, traces, evidence of places in the code that are a bottleneck that would necessitate another library to solve the problem...

@zadjii-msft commented on GitHub (Mar 3, 2020): I mean I'm not sure how just "adding Boost" to the terminal would be a magic bullet to get a perf gain out of the Terminal - we'd need actual logs, traces, evidence of places in the code that are a bottleneck that would _necessitate_ another library to solve the problem...
claunia commented 2026-01-31 00:45:16 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 4, 2020):

If the theory is that DX is to blame, you could probably confirm that by comparing the performance of a conhost session with and without the UseDx registry setting.

@j4james commented on GitHub (Mar 4, 2020): If the theory is that DX is to blame, you could probably confirm that by comparing the performance of a conhost session with and without the `UseDx` registry setting.
claunia commented 2026-01-31 00:45:16 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 5, 2020):

This seems like another version of /dup #1064, and #778 should help with it.

@DHowett-MSFT commented on GitHub (Mar 5, 2020): This seems like another version of /dup #1064, and #778 should help with it.
claunia commented 2026-01-31 00:45:16 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 5, 2020):

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 (Mar 5, 2020): 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Performance Product-Terminal Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6704
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?