cmd execution and GCC compilation scripts slow #550

Open
opened 2026-01-30 21:55:04 +00:00 by claunia · 0 comments
Owner

Originally created by @kjarvel on GitHub (Feb 6, 2019).

Configuration

Windows build number:

  • Windows 7 SP1: Microsoft Windows [Version 6.1.7601]
  • Windows 10 1809: Microsoft Windows [Version 10.0.17763.253]

What you're doing and what's happening:

With Windows 7, executing build_gcc.bat (1000 x gcc-arm-none-eabi) in Command Prompt takes 0:46.
With Windows 10, the same script takes +78% longer time with default settings (01:22).

With Windows 7, executing build_cmd.bat (1000 x cmd.exe x 20) in Command Prompt takes 01:48.
With Windows 10, the same script takes +139% longer time with default settings (04:18).

Some observations:
With Windows 10, some computers show heavy (25-40%) GPU load when Command Prompt is scrolling.
A Windows 7 Virtual Machine running build_cmd.bat in Virtual Box on a Windows 10 host outperforms the Windows 10 host.

The strange thing is that starting Command Prompt with "Run as Administrator" on Windows 10 increases performance a lot - back to Windows 7 level. Using the "Legacy Console mode" checkbox only seems to have a minor effect.

See attached scripts and results.txt.
scripts.zip
results.txt

What's wrong / what should be happening instead:

Windows 10 Command Prompt performance for build_cmd.bat and build_gcc.batshould be the same as with Windows 7, or at least the same as Windows 10 Command Prompt running as Administrator.

(The problem is that running a 10 minute build script might take 20+ minutes on Windows 10)

Originally created by @kjarvel on GitHub (Feb 6, 2019). **Configuration** * CPU: Intel Core i5-4590 @ 3.30 GHz * Windows 7 Anti-Virus: Microsoft Security Essentials * Windows 10 Anti-Virus: Microsoft Windows Defender * Display 1920 x 1080, Scaling 100% * GCC Arm compiler gcc-arm-none-eabi-8-2018-q4-major-win32-sha2.exe from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads **Windows build number:** - Windows 7 SP1: Microsoft Windows [Version 6.1.7601] - Windows 10 1809: Microsoft Windows [Version 10.0.17763.253] **What you're doing and what's happening:** With Windows 7, executing `build_gcc.bat` (1000 x gcc-arm-none-eabi) in Command Prompt takes 0:46. With Windows 10, the same script takes +78% longer time with default settings (01:22). With Windows 7, executing `build_cmd.bat` (1000 x cmd.exe x 20) in Command Prompt takes 01:48. With Windows 10, the same script takes +139% longer time with default settings (04:18). Some observations: With Windows 10, some computers show heavy (25-40%) GPU load when Command Prompt is scrolling. A Windows 7 Virtual Machine running `build_cmd.bat` in Virtual Box on a Windows 10 host outperforms the Windows 10 host. The strange thing is that starting Command Prompt with "Run as Administrator" on Windows 10 increases performance a lot - back to Windows 7 level. Using the "Legacy Console mode" checkbox only seems to have a minor effect. See attached scripts and `results.txt`. [scripts.zip](https://github.com/Microsoft/console/files/2836535/scripts.zip) [results.txt](https://github.com/Microsoft/console/files/2836536/results.txt) **What's wrong / what should be happening instead:** Windows 10 Command Prompt performance for `build_cmd.bat` and `build_gcc.bat`should be the same as with Windows 7, or at least the same as Windows 10 Command Prompt running as Administrator. (The problem is that running a 10 minute build script might take 20+ minutes on Windows 10)
claunia added the Product-ConhostIssue-BugNeeds-Tag-FixArea-PerformancePriority-1 labels 2026-01-30 21:55:04 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#550