Possible build time regression on empty macOS (Arm64) projects
See original GitHub issueDescribe the bug
- I was starting a new .NET 6 console project on a MacBook Pro (M1 Max, 10 Cores) via the CLI:
dotnet new console
- When building the empty project, the build time is almost 3 seconds, but the real time it takes all in all is closer to 4-5 seconds.
- I felt a build of a new “Hello, world” console project should not take that long, so I made a thread in the .NET subreddit about it: https://www.reddit.com/r/dotnet/comments/u6axwd/net_6_compilation_speed_on_macos_monterey_am_i/
- In this thread,
u/andyayers
(@AndyAyersMS) pointed me towards this repository, suggesting this might be a performance bug: https://www.reddit.com/r/dotnet/comments/u6axwd/net_6_compilation_speed_on_macos_monterey_am_i/i5cy23x/
To Reproduce
- Download and install the latest .NET 6 SDK on macOS Monterey 12.3.1 (my machine is a MacBook Pro (14-inch, 2021) M1 Max)
- Create a new .NET console application via
dotnet new console
- Build the application via
dotnet build
Exceptions (if any)
Further technical details
- Include the output of
dotnet --info
.NET SDK (reflecting any global.json):
Version: 6.0.102
Commit: 02d5242ed7
Runtime Environment:
OS Name: Mac OS X
OS Version: 12.3
OS Platform: Darwin
RID: osx.12-arm64
Base Path: /usr/local/share/dotnet/sdk/6.0.102/
Host (useful for support):
Version: 6.0.2
Commit: 839cdfb0ec
.NET SDKs installed:
6.0.102 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
- The IDE (VS / VS Code/ VS4Mac) you’re running on, and its version
No IDE necessary for this, but I’m using VSCode 1.66.2
Issue Analytics
- State:
- Created a year ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Inconsistent macOS architecture handling on Apple Silicon ...
I've confirmed that by building a CMake targeting arm64 , and one targeting x86_64 . Here's the results of running them on the...
Read more >Cannot debug net6.0-macos Apps - Developer Community
When I hit debug, the following error is shown in the Terminal: Possible reasons for this include: * You misspelled a built-in dotnet...
Read more >macOS: Support arm64 #78710 - Blender developer
I want to learn Blender, but I'm not in a specific hurry, therefore I'll wait for a native apple silicon version and start...
Read more >Android IL2CPP build times really slow
How can be possible that an EMPTY project needs 13 minutes to build an apk? And on mono2x it's 1 minute or less....
Read more >Swift 5.7 / Xcode 14 incremental build time 10x slower than ...
With just a slightly modification on my Swift project, incremental build on Xcode 13 takes about 10 seconds to complete, but on 14,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree such a cleanup would be sensible, @kopkako. I wasn’t even aware of the
dotnet-sdk
cask. The most important difference between thedotnet
anddotnet-sdk
casks seems to bedotnet-runtime
vs.dotnet-sdk
:The
dotnet
formula installs the SDK, not the runtime. As such, it’s easy to argue thatdotnet-sdk
would have been a better name for the formula. Either way, we could petition for the deletion of thedotnet-sdk
cask, since thedotnet
formula is a source-built, and thus more portable, alternative.The latter. Folks can open an issue on the appropriate community project.
We can close this issue now.