Skip to content

Commit b70f978

Browse files
committed
draft
1 parent fa6e3fe commit b70f978

File tree

3 files changed

+51
-52
lines changed

3 files changed

+51
-52
lines changed

docs/build-insights/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ items:
66
- name: "Tutorials"
77
expanded: true
88
items:
9-
- name: "Troubleshoot function inlining on build time"
9+
- name: "Troubleshoot function inlining impact on build time"
1010
href: ../build-insights/tutorials/build-insights-function-view.md
1111
- name: "Troubleshoot template instantiation impact on build time"
1212
href: ../build-insights/tutorials/build-insights-template-view.md

docs/build-insights/tutorials/build-insights-function-view.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: "Troubleshoot function inlining on build time"
2+
title: "Troubleshoot function inlining impact on build time"
33
description: "Tutorial for how to use Build Insights function view to troubleshoot the impact of function inlining on build time in your C++ projects."
44
ms.date: 5/30/2024
55
helpviewer_keywords: ["C++ Build Insights", "inline function analysis", "build time analysis", "__forceinline analysis", "inlines analysis"]
66
ms.topic: troubleshooting-general
77
---
8-
# Troubleshoot function inlining on build time
8+
# Troubleshoot function inlining impact on build time
99

1010
Use Build Insights **Functions** view to troubleshoot the impact of function inlining on build time in your C++ projects.
1111

@@ -128,8 +128,8 @@ Double-click, right-click, or press **Enter** while on a file in the **Functions
128128
129129
## Tips
130130
131-
- You can **File** > **Save As** the ETL file to a more permanent location to keep a record of the build time. You can then compare it to future builds to see if your changes are improving build time.
132-
- If you inadvertently close the Build Insights window, reopen it by finding the `<dateandtime>.etl` file in your temporary folder. The `TEMP` Windows environment variable provides the path of your temporary files folder.
131+
- Use **File** > **Save As** to save the ETL file to a more permanent location to keep a record of the build time information. You can then compare it to future builds to see how your changes are improving things.
132+
- If you close the Build Insights window, reopen it by finding the `<dateandtime>.etl` file in your temporary folder. The `TEMP` Windows environment variable provides the path of your temporary files folder.
133133
- To dig into the Build Insights data with Windows Performance Analyzer (WPA), click the **Open in WPA** button in the bottom right of the ETL window.
134134
- Drag columns to change the order of the columns. For instance, you may prefer moving the **Time** column to be the first column. You can hide columns by right-clicking on the column header and deselecting the columns you don't want to see.
135135
- The **Functions** view provides a filter box to find a function that you're interested in. It does partial matches on the name you provide.

0 commit comments

Comments
 (0)