-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd execution and GCC compilation scripts slow #368
Comments
Update one year later:
build_cmd.bat
|
did you try disabling windows defender real time protection to measure the performance? |
Yes, see the column named "Anti-virus" in results.txt. |
Is this specific to gcc or also observable with MSVC ? |
See build_cmd.bat and the results for build_cmd.bat in results.txt. It does not use gcc. |
You know, this is weird. I'd be fairly sure that checking the "use legacy console" checkbox would remove the issue, if it was something in the Console v2 codebase. That's pretty literally the exact code from the Windows 7 build, with only minor modifications to get it loaded into the v2 console. We've been making pretty constant perf improvements over the years (case in point: #1064 (comment)). At this point, the Terminal is generally faster than the Console at all. If you're still seeing this, would you mind trying to trace your build (or at least part of it) with WPA? I think we'd all be curious to see what the hot paths are. |
Thanks for the response. You can easily try this yourself, it requires no external dependencies, and you will see the same results. My results now in 2021, performed on the same computer:
Conclusion: Windows 7 runs the script twice as fast, even when running in a Virtual machine, on the same computer. See attached video. Windows 7 to the left. Windows 11 to the right: |
Configuration
https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads
Windows build number:
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
andbuild_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)
The text was updated successfully, but these errors were encountered: