Skip to content

Commit 86c1d36

Browse files
Merge pull request #10627 from Mikejo5000/mikejo-br16
Edit instrumentation docs for profiling
2 parents ea6fda1 + dc102bf commit 86c1d36

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/profiling/understanding-performance-collection-methods-perf-profiler.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,6 @@ Instrumentation profiling collects detailed information about the work that is p
3838

3939
## Sampling versus instrumentation
4040

41-
The value of sampling is that it has less overheard and for this reason is more likely to be statistically representative of the application running in production. The value of instrumentation profiling is that you can get exact call counts on how many times your functions were called. This gives you much more detailed information than normal sampling, which can distort the time taken in some scenarios. For example, functions that don't do much, but are called frequently, will show up more than they would in a real world scenario.
41+
The value of sampling is that it has less overhead and for this reason is more likely to be statistically representative of the application running in production. The value of instrumentation profiling is that you can get exact call counts on how many times your functions were called. This gives you much more detailed information than normal sampling, which can distort the time taken in some scenarios. For example, functions that don't do much, but are called frequently, will show up more than they would in a real world scenario.
4242

43-
With instrumentation, every function call in your application is annotated and instrumented so that when it gets invoked it's added to the trace along with information about the caller. With sampling, the current call stack executing is polled from the CPU at an interval and then each frame is added to the trace.
43+
With instrumentation, every function call selected in your application is annotated and instrumented so that when it gets invoked it's added to the trace along with information about the caller. With sampling, the current call stack executing is polled from the CPU at an interval and then each frame is added to the trace.

0 commit comments

Comments
 (0)