Chrome DevTools Performance Profiler Settings
We learn about the various settings options in the performance profiler dev-tools tab. We look at how we can leverage these settings to get relevant profiling information. The screenshots checkbox makes sure that the profile records screenshots for every frame that was rendered. This gives a good idea of loading order. The memory checkbox hides/shows memory usage details.
You can disable javascript recordings, or enable deeper render information for more relevant profiles.
The network dropdown lets you simulate different network conditions, offline and allows configuration to add custom settings. The CPU dropdown lets you test different CPU conditions simulating slower devices and mobile device performance.
Pavithra Kodmad: [0:00] Make sure the screenshots option is selected. This allows the profiler to record screenshots during regular intervals. The memory option shows us the memory allocations during the recording, along with the detailed splits and analysis.
[0:16] Click on the settings icon here to open the Capture settings menu. There are two toggle options and two dropdowns here. The Disable JavaScript Samples option allows you to remove the JavaScript samples and only focus on render and paint instrumentation. Enabling advanced paint instrumentation will gather more details for your profile, but at the cost of speed of operation.
[0:40] In the Network dropdown, there are options to simulate different network bandwidths -- online by default, fast and slow 3G, even offline, and custom setups that you can create yourself. Custom setups help you represent specific circumstances for your testing.
[1:00] Under the CPU dropdown, we have options that simulate less powerful CPUs than developer laptops, mostly mitering throttle the CPUs in mobile settings.
[1:11] In summary, these are all settings that you can use to capture relevant performance data in an efficient manner.
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!