Stefan Oehme
Gradle Summit
Palo Alto · June 22 - 23, 2017
Performance Team Lead at Gradle
Gradle core engineer for over a year. Contributor to Eclipse Buildship.
Presentations
Identifying and addressing build performance problems
Your build can never be fast enough if you want to keep your team happy and in the flow. The first challenge is to realize that there is a problem: You will learn how to use Gradle Enterprise to find the biggest performance bottlenecks that your team is facing. We will then use Build Scans and the Gradle Profiler to analyze the root causes of these badly performing builds. Finally, we will show you how to fix some of the most common problems like: Slow configuration time, tasks running when they shouldn't, and builds that don't parallelize well. Given these tools and knowledge you will be able to make your builds a lot faster, often by an order of magnitude.
Android Performance Pitfalls
While developing Gradle 4.0 and the Android Plugin 2.5, the Gradle and Android Studio teams looked at a lot of real-world builds and their performance. Many of the bottlenecks could be addressed transparently by improving Gradle and the Android plugin. Other issues are caused by misconfiguration or an inefficient project structure. In this session we will show you the most common performance pitfalls for Android projects and how to fix them.
Profiling Android Builds
You have updated to the latest Android Plugin and avoided the most common performance pitfalls, but your Android build is still not as as fast as you wish it to be? Then this talk is for you. We will use build scans to pinpoint performance bottlenecks like non-incremental tasks and inefficient plugins or build scripts. For issues that require more low-level investigation, the Gradle profiler will provide us with the necessary data. Equipped with these tools, no performance problem will be able to hide from you for long.