2017-06-07 15:49:20 +00:00
|
|
|
# Profiling Desktop using the Chrome Developer Tools
|
|
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
Sometimes performance issues are hard to identify and recreate. If you notice
|
|
|
|
|
a regression and can reproduce it, you can use the Timeline tools in Chrome Dev
|
2017-06-07 15:49:20 +00:00
|
|
|
Tools to take a snapshot of the application performance and attach it to an
|
|
|
|
|
issue.
|
|
|
|
|
|
|
|
|
|
## Steps
|
|
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Launch Desktop and select **View** | **Toggle Developer Tools**.
|
|
|
|
|
|
2017-06-07 15:58:32 +00:00
|
|
|
<img width="558" src="https://user-images.githubusercontent.com/359239/26888284-f80ed244-4b80-11e7-86cf-933c59b8f370.png">
|
|
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Get the Desktop application ready to perform the problem action.
|
2018-10-14 20:16:59 +00:00
|
|
|
- Select the **Performance** tab. Ensure the **Disable JavaScript samples** option is **unchecked**.
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-10-14 20:16:59 +00:00
|
|
|
<img width="972" src="https://user-images.githubusercontent.com/359239/46921615-e9a8c100-cfd3-11e8-9a0f-eac7fda611f6.png">
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Press the **Record** button on the left to start recording.
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-10-14 20:16:59 +00:00
|
|
|
<img width="1051" src="https://user-images.githubusercontent.com/359239/46921640-3be9e200-cfd4-11e8-937b-b3ebbebaab68.png">
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Perform the problem action in Desktop. Try and keep the test focused on the
|
|
|
|
|
issue you're seeing.
|
|
|
|
|
- Switch back to the Developer tools and press **Stop** to complete recording.
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-10-14 20:16:59 +00:00
|
|
|
<img width="1050" src="https://user-images.githubusercontent.com/359239/46921658-8a977c00-cfd4-11e8-86ed-d4b6878f08c5.png">
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-10-14 20:16:59 +00:00
|
|
|
- In the header, click the **Save profile...** menu item. Save the JSON file
|
|
|
|
|
somewhere you can access later.
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-10-14 20:16:59 +00:00
|
|
|
<img width="405" src="https://user-images.githubusercontent.com/359239/46921672-b450a300-cfd4-11e8-98c6-cba2b3eef1b8.png">
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Compress the JSON file to reduce the file size (it could be 10MB or more
|
|
|
|
|
depending on how long you ran the test for).
|
2017-06-07 15:49:20 +00:00
|
|
|
|
2018-02-01 23:08:53 +00:00
|
|
|
- Attach the file to your GitHub issue so the contributors can load this into
|
|
|
|
|
their environment and spelunk the diagnostic information.
|
