You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: aspnetcore/blazor/performance/webassembly-browser-developer-tools-diagnostics.md
-16Lines changed: 0 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,33 +169,17 @@ Property | Default | Set value to… | Description
169
169
`<WasmProfilers>` | No value | `browser` | Mono profilers to use. Potential values are "`browser`" and "`log`". To use both, separate the values with a semicolon. The `browser` profiler enables integration with the browser's developer tools profiler.
170
170
`<WasmPerfTracing>` | `false` | `true` | Controls diagnostic server tracing.
171
171
`<WasmPerfInstrumentation>` | `false` | `true` | Controls CPU sampling instrumentation for diagnostic server.
172
-
`<MetricsSupport>` | `false` | `true` | Controls `System.Diagnostics.Metrics` support. For more information, see the [`System.Diagnostics.Metrics` namespace](/dotnet/api/system.diagnostics.metrics).
173
-
`<EventSourceSupport>` | `false`| `true` | Controls `EventPipe` support. For more information, see [Diagnostics and instrumentation: Observability and telemetry](/dotnet/core/deploying/native-aot/diagnostics#observability-and-telemetry).
The [`Timing-Allow-Origin` HTTP header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Timing-Allow-Origin) allows for more precise time measurements.
186
182
187
-
Browser developer tools console calls in the following example that trigger profiling:
188
-
189
-
*`collectGcDump`: Collect a GC (Garbage Collector) dump.
190
-
*`collectPerfCounters(durationSeconds)`: Collect general performance counters.
191
-
*`collectCpuSamples(durationSeconds)`: Collect CPU performance counters.
0 commit comments