Skip to content

Commit 5df75a8

Browse files
authored
Merge pull request #50424 from fliang-ms/UpdateResultZipFileName
update scenario name and result zip file name
2 parents 7dd5523 + e118056 commit 5df75a8

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/virtual-machines/windows/how-to-use-perfInsights.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ If you are experiencing performance problems with virtual machines, before conta
2727

2828
PerfInsights can collect and analyze several kinds of information. The following sections cover common scenarios.
2929

30-
### Quick Performance Analysis
30+
### Quick performance analysis
3131

3232
This scenario collects the disk configuration and other important information, including:
3333

@@ -61,11 +61,11 @@ This scenario runs the [Diskspd](https://github.com/Microsoft/diskspd) benchmark
6161
> This scenario can affect the system, and shouldn’t be run on a live production system. If necessary, run this scenario in a dedicated maintenance window to avoid any problems. An increased workload that is caused by a trace or benchmark test can adversely affect the performance of your VM.
6262
>
6363
64-
### Performance Analysis
64+
### Performance analysis
6565

6666
This scenario runs a [performance counter](https://msdn.microsoft.com/library/windows/desktop/aa373083(v=vs.85).aspx) trace by using the counters that are specified in the RuleEngineConfig.json file. If the VM is identified as a server that is running SQL Server, a performance counter trace is run. It does so by using the counters that are found in the RuleEngineConfig.json file. This scenario also includes performance diagnostics data.
6767

68-
### Azure Files Analysis
68+
### Azure Files analysis
6969

7070
This scenario runs a special performance counter capture together with a network trace. The capture includes all the Server Message Block (SMB) client shares counters. The following are some key SMB client share performance counters that are part of the capture:
7171

@@ -87,7 +87,7 @@ This scenario runs a special performance counter capture together with a network
8787
| | Avg. Write Queue Length |
8888
| | Avg. Data Queue Length |
8989

90-
### Advanced Performance Analysis
90+
### Advanced performance analysis
9191

9292
When you run an advanced performance analysis, you select traces to run in parallel. If you want, you can run them all (Performance Counter, Xperf, Network, and StorPort).
9393

@@ -101,7 +101,7 @@ Information about Windows VM, disks or storage pools configuration, performance
101101

102102
|Data collected | | | Performance scenarios | | | |
103103
|----------------------------------|----------------------------|------------------------------------|--------------------------|--------------------------------|----------------------|----------------------|
104-
| | Quick Performance Analysis | Benchmarking | Performance Analysis | Azure Files Analysis | Advanced Performance Analysis |
104+
| | Quick performance analysis | Benchmarking | Performance analysis | Azure Files analysis | Advanced performance analysis |
105105
| Information from event logs | Yes | Yes | Yes | Yes | Yes |
106106
| System information | Yes | Yes | Yes | Yes | Yes |
107107
| Volume map | Yes | Yes | Yes | Yes | Yes |
@@ -168,9 +168,9 @@ Diskspd I/O workload tests (OS Disk [write] and pool drives [read/write])
168168

169169
#### Possible problems when you run the tool on production VMs
170170

171-
- For the benchmarking scenario or the "Advanced Performance Analysis" scenario that is configured to use Xperf or Diskspd, the tool might adversely affect the performance of the VM. These scenarios should not be run in a live production environment.
171+
- For the benchmarking scenario or the "Advanced performance analysis" scenario that is configured to use Xperf or Diskspd, the tool might adversely affect the performance of the VM. These scenarios should not be run in a live production environment.
172172

173-
- For the benchmarking scenario or the "Advanced Performance Analysis" scenario that is configured to use Diskspd, ensure that no other background activity interferes with the I/O workload.
173+
- For the benchmarking scenario or the "Advanced performance analysis" scenario that is configured to use Diskspd, ensure that no other background activity interferes with the I/O workload.
174174

175175
- By default, the tool uses the temporary storage drive to collect data. If tracing stays enabled for a longer time, the amount of data that is collected might be relevant. This can reduce the availability of space on the temporary disk, and can therefore affect any application that relies on this drive.
176176

@@ -242,11 +242,11 @@ To run the PerfInsights tool, follow these steps:
242242
>
243243
>If the duration switch **/d** is not specified, PerfInsights will prompt you to repro the issue while running vmslow, azurefiles and advanced scenarios.
244244
245-
When the traces or operations are completed, a new file appears in the same folder as PerfInsights. The name of the file is **CollectedData\_yyyy-MM-dd\_hh-mm-ss-fff.zip.** You can send this file to the support agent for analysis or open the report inside the zip file to review findings and recommendations.
245+
When the traces or operations are completed, a new file appears in the same folder as PerfInsights. The name of the file is **PerformanceDiagnostics\_yyyy-MM-dd\_hh-mm-ss-fff.zip.** You can send this file to the support agent for analysis or open the report inside the zip file to review findings and recommendations.
246246
247247
## Review the diagnostics report
248248
249-
Within the **CollectedData\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file, you can find an HTML report that details the findings of PerfInsights. To review the report, expand the **CollectedData\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file, and then open the **PerfInsights Report.html** file.
249+
Within the **PerformanceDiagnostics\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file, you can find an HTML report that details the findings of PerfInsights. To review the report, expand the **PerformanceDiagnostics\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file, and then open the **PerfInsights Report.html** file.
250250
251251
Select the **Findings** tab.
252252
@@ -311,4 +311,4 @@ The following screenshot shows a message similar to what you might receive:
311311
312312
Follow the instructions in the message to access the file transfer workspace. For additional security, you have to change your password on first use.
313313
314-
After you sign in, you will find a dialog box to upload the **CollectedData\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file that was collected by PerfInsights.
314+
After you sign in, you will find a dialog box to upload the **PerformanceDiagnostics\_yyyy-MM-dd\_hh-mm-ss-fff.zip** file that was collected by PerfInsights.

0 commit comments

Comments
 (0)