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

Create a connection for simple testing Windows Terminal performance #5625

New Issue
Open
opened 2026-01-31 00:17:44 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 00:17:44 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Dec 17, 2019).

Right now, the Windows Terminal's perf is pretty tightly bound to the perf of conpty. It might be a little hard for us to be able to really analyze the performance bottlenecks of the Terminal, if we're also hitting the bottlenecks of conpty in another thread.

To aid in debugging, I think we should add another connection implementation. This connection should only be valuable for debugging and perf testing. I'm imagining something where it can be configured to emit some number of lines of text, either in monochrome, 16 color, or 256/rgb color, and then it just times how long it takes to emit that sequence. It'll emit all that text, then just print statistics on how long it took to emit all that text.

Ideas for settings: (though I'm not sure if this is too much work)

{
    "name": "Perf test",
    "connectionType": "some guid",
    "linesToTest": 10000, // or -1 for run without stopping
    "colors": "monochrome", // or "16color", "256color"
    "style": "ascii" // or unicode for CJK/emoji
},

This way, we can get traces on just the Terminal, isolated from conpty.

Originally created by @zadjii-msft on GitHub (Dec 17, 2019). Right now, the Windows Terminal's perf is pretty tightly bound to the perf of conpty. It might be a little hard for us to be able to really analyze the performance bottlenecks of the Terminal, if we're also hitting the bottlenecks of conpty in another thread. To aid in debugging, I think we should add another connection implementation. This connection should only be valuable for debugging and perf testing. I'm imagining something where it can be configured to emit some number of lines of text, either in monochrome, 16 color, or 256/rgb color, and then it just times how long it takes to emit that sequence. It'll emit all that text, then just print statistics on how long it took to emit all that text. Ideas for settings: (though I'm not sure if this is too much work) ```jsonc { "name": "Perf test", "connectionType": "some guid", "linesToTest": 10000, // or -1 for run without stopping "colors": "monochrome", // or "16color", "256color" "style": "ascii" // or unicode for CJK/emoji }, ``` This way, we can get traces on _just_ the Terminal, isolated from conpty.
claunia commented 2026-01-31 00:17:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 17, 2019):

Depends on #4003.

@DHowett-MSFT commented on GitHub (Dec 17, 2019): Depends on #4003.
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 Area-TerminalConnection Issue-Task Product-Terminal
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#5625
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?