Once it’s done publishing, you will get a link on the terminal to check your build scan. Once the build completes successfully, it will prompt you to accept the terms of service to upload your build scan results. Fire up the terminal on Android Studio and execute the following command. Gradle has a handy scan option that you can use to analyze the performance of your task. But first!īefore starting off with the optimization, it’s important to benchmark our project to see how long it currently takes to build. ![]() But I am going to intentionally focus on the minor, painless measures I took to come close to this metric for the sake of keeping this post beginner friendly. It’s easy to go overboard with optimizations that you can perform to bring down your build time even further. ![]() Going down from 5.5 minutes to 17 seconds? That’s bonkers. pre-optimisation ? post-optimization ⚡️⚡️ To give you a sneak peek of the time I was able to shed from our clean builds, here’s a before and after metric from the build scan. Gradle has always had a bad rep for being slow and resource intensive, but I was quite surprised at how minor changes to the project’s build configuration could massively improve the build speeds. It seemed like the perfect opportunity to try and fix the build speeds of the project. Recently, I undertook the task of migrating the Android codebase at Kure to AndroidX.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |