Skip to content

Commit 3a30f36

Browse files
committed
Updates
1 parent 895c85a commit 3a30f36

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

aspnetcore/blazor/performance/profiling.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ Invoke `{APP NAMESPACE}.Profiling.TakeHeapshot()` from your code in order to cre
129129
[EventPipe](/dotnet/core/diagnostics/eventpipe) is a runtime component used to collect tracing data, similar to [ETW](/windows/win32/etw/event-tracing-portal) and [perf_events](https://wikipedia.org/wiki/Perf_%28Linux%29).
130130

131131
* Manual testing
132-
* Browser developer tools: Download, open in Visual Studio, and find expected calls.
132+
* Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find expected calls.
133133
* [`dotnet-trace`](/dotnet/core/diagnostics/dotnet-trace): Open the `.nettrace` output file in Visual Studio and find the expected method calls.
134134
* Web-based testing
135135
* Use the JavaScript API to obtain a [promise](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) of NetTrace (`.nettrace`) bytes.
@@ -145,7 +145,7 @@ Built-in performance counters are available to track:
145145
## GC (Garbage Collector) dumps
146146

147147
* Manual testing
148-
* Browser developer tools: Download, open in Visual Studio, and find the expected classes.
148+
* Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find expected calls.
149149
* [`dotnet-gcdump` (`collect`/convert` options)](/dotnet/core/diagnostics/dotnet-gcdump): To view the captured GC dump files, see [View the GC dump captured from dotnet-gcdump](/dotnet/core/diagnostics/dotnet-gcdump#view-the-gc-dump-captured-from-dotnet-gcdump).
150150
* Web-based testing
151151
* Use the JavaScript API to obtain a [promise](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) of NetTrace (`.nettrace`) bytes.
@@ -155,7 +155,7 @@ Built-in performance counters are available to track:
155155
## Counters trace
156156

157157
* Manual testing
158-
* Browser developer tools: Download, open in Visual Studio, and find the expected counters/values.
158+
* Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find expected calls.
159159
* [`dotnet-counters collect`](/dotnet/core/diagnostics/dotnet-counters): Open the `.csv`/`.json` output file in Visual Studio and find the expected counters/values.
160160
* Web-based testing
161161
* Use the JavaScript API to obtain a [promise](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) of NetTrace (`.nettrace`) bytes.

0 commit comments

Comments
 (0)