![]() We are coming to the central part of this article: the results. Results of comparing M1 Mini vs Mac Pro vs Mac Mini You can also take a look at this spreadsheet, which shows all the raw data and links to the builds. For example, the later build time for the iOS Counter app is the average time of three builds. We ran every build three times and calculated the average. CocoaPods cache: HOME/Library/Caches/CocoaPodsįor more information about how to use caching in Codemagic, just take a look at the documentation on dependency caching.For caching, we cached the following paths: We compared the builds without and with caching. To get a more realistic view, all builds used the release mode of Flutter.įor the tests, we just used the flutter test command. These machines have the following configuration: We are using Codemagic’s virtual machines for the test, which you can use for CI/CD. Therefore, you will see very realistic build times. It uses a bunch of dependencies, like many of the Firebase packages and several other ones (Sharezone is open source - you can find all the dependencies here). In the comparison, we focus more on the Sharezone app because Sharezone is a real production app with +300,000 registered users. Sharezone - an open-source school planner students, parents, and teachers can use to organize together.To compare the builds of the Flutter apps, we used two apps: Which apps have been used for the builds?.Let’s talk about the setup of this comparison and take a look at questions like: This article is written by Nils Reichardt and originally posted to Codemagic blog ![]() In this article, we’ll give you the facts and figures you need to decide if an upgrade is worth it. So we know that M1 machines are fast, but should we use them in CI/CD to speed up our pipeline? To help answer that question, we compared the M1 mini, Mac Pro, and Mac mini for iOS and macOS builds with Codemagic. Perhaps you already read the tweet by Jameson Williams (a staff software engineer at Reddit): Since then, we have all read and heard from other people about the crazy performance improvements. ![]() In November 2020, Apple released the M1 MacBook and, one year later, the M1 Pro/Max chips. Tracking Apple Silicon as a host device separately at #60118.TL DR: M1 machines are astonishingly fast! For iOS builds (with caching), we see build time improvements of ~50% compared with the Mac Pros. CocoaPods compatibility with Apple DTK (Apple Silicon) CocoaPods/CocoaPods#9907.macOS xcode project should move Framework linking to tool #56581.Add macOS architecture to doctor output #65976. ![]() Adjust lipo thinning input/output for macOS #97111.Adds scripts for cross-arch macOS framework engine#31014.amework engine isn't natively available for desktop for ARM macOS Apple Sillicon (including building for all valid architectures on x86) #69221.Add integration tests to validate architectures of built macOS app #97978.Run macOS integration tests on M1 Macs #97977.Use ARM macOS frameworks, gen_snapshot_圆4 and gen_snapshot_arm64 in the tool #97681.Add Mac M1 ARM machines to the prod pool #87508.potentially adding new options to control what is being targeted.Updating the tool to understand the new target.Building/uploading engine artifacts in the correct format.We can add specific sub-issues over time, but at a high level this will involve: Filing as an umbrella bug for the overall feature of building ARM macOS applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |