This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Both WT and Powershell are great, but the startup is a little slow when combined together. And my some thoughts. #17642
Labels
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Needs-Tag-Fix
Doesn't match tag requirements
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Description of the new feature/enhancement
As the title described. On my computer(AMD Ryzen 3600, even slower on Snapdragon 8cx Gen 3):
I do want to help, but after some digging into the code, it quickly turn out that its complexity is far beyond my level. However I think the ideas maybe somehow helpful for core team, so I just take some time to this.
Proposed technical implementation details (optional)
Start profile's command line as early as possible, ideally right after settings loaded. Then the startup of pwsh.exe will overlap with UI initialization. However I don't know it's valid or not, as I am not familiar with terminal things.
Made subsequent process run faster. Currently it need to load the whole settings to get the value of
compatibility.isolatedMode
, which in turn cause time-consumingWindowsXamlManager::InitializeForCurrentThread()
inApp::App()
. It should be avoided, or better, avoid loading the whole settings too.Create spare window thread on idle time after new window showed. Add an option to allow keep running in background just like Edge and tweak auto launch on boot to adapt it. Now event if the first is hard to implement and pwsh.exe is still slow to start, we at least always get quick UI response.
The text was updated successfully, but these errors were encountered: