Timeline for Why are Windows Terminal and PowerShell so very inefficient compared to cmd.exe, and how to make them fast?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2023 at 14:23 | comment | added | Majd | @user1686 I tried your suggestion to turn on the Atlas engine thing, but it's the same thing: launching many terminals at once makes my system crawl on its knees, whereas cmd.exes can be launched without even noticing it. | |
| Apr 7, 2023 at 14:07 | comment | added | Majd | @user1686 I really, truly have no idea what you're saying. Whatever goes on "behind the scenes", internally in Windows, my question remains and has not been answered whatsoever. :/ And extreme CPU usage and lots of RAM usage cannot be attributed to GPU rendering... | |
| Apr 7, 2023 at 9:29 | comment | added | grawity_u1686 | Right, but do not lump "(powershell/windows terminal)conhost" all into one thing – that makes no sense. Windows Terminal is not Conhost (though it does use a conhost-like "openconsole.exe" shim internally), and it's not even in the same category as PowerShell (which is not any kind of terminal or console at all, it's just a CLI shell). I'm not surprised that WT uses more resources than Conhost (both for the terminal app as a whole and for each additional text buffer), but that's completely independent from e.g. PowerShell being slower to initialize. | |
| Apr 7, 2023 at 9:07 | comment | added | GChuf | I understand your question now. In my own experience, the binary performs the same. It's the (powershell/windows terminal)conhost process that takes a lot of memory, and a lot of time to start up. | |
| Apr 7, 2023 at 9:00 | comment | added | grawity_u1686 | Again, which part of it? Does the binary itself occupy more memory or take more CPU to perform the same task when it's run from within PowerShell, or does PowerShell just take longer to spawn the binary initially? Is it the binary, or the PowerShell process, or the Conhost/WindowsTerminal process that's using those resources? | |
| Apr 7, 2023 at 8:45 | comment | added | GChuf | "the other program" as you put it is just a binary that does something. The whole problem is that calling that binary through windows terminal or powershell is slower and hogs more resources than cmd. Hence the question how to make that faster. | |
| Apr 7, 2023 at 8:39 | comment | added | grawity_u1686 | Depends on which part of it is actually slower? PowerShell itself is slow to start up, but I'm not sure when the "other program" comes in, in your case. | |
| Apr 7, 2023 at 8:35 | comment | added | GChuf | If they all use the same console window, why is powershell so much slower? Why does the OP experience different results? I can attest to cmd.exe being faster than powershell.exe for running multiple instances of another program. | |
| Apr 7, 2023 at 8:34 | history | edited | grawity_u1686 | CC BY-SA 4.0 |
added 547 characters in body
|
| Apr 7, 2023 at 8:27 | history | answered | grawity_u1686 | CC BY-SA 4.0 |