Tooling Techniques for the Performance Ninja
Stay organized with collections
Save and categorize content based on your preferences.
Knowing your way around your development tools is key to becoming a performance expert. Colt stepped through the three pillars of performance: network, compute and render, providing a tour of the key problem in each area and the tools available for finding and eradicating them.
Slides
- You can now profile Chrome on Android with the DevTools you know and love from desktop.
- The iteration loop for performance work is: gather data, achieve insight, take action.
- Prioritize assets that are on the critical rendering path for your pages.
- Avoid painting; it’s super expensive.
- Avoid memory churn and executing code during critical times in your app.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-06 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["Chrome DevTools can be used to profile performance on both desktop and Android, focusing on network, compute, and rendering aspects."],["Optimizing performance involves a continuous loop of gathering data, gaining insights, and taking action based on findings."],["Prioritizing critical rendering path assets, minimizing paint operations, and reducing memory churn are crucial for enhancing web performance."]]],["The core of performance optimization involves understanding network, compute, and rendering challenges. Key actions include profiling Chrome on Android using familiar DevTools, prioritizing assets on the critical rendering path, and minimizing painting. The performance workflow is iterative: collect data, gain insights, and act. Crucial is avoiding memory churn and code execution during critical application phases. These actions help identify and resolve performance bottlenecks.\n"]]
