From f1c948536d6f4b9025b8593dc3f285f3ccf84db6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alex=20R=C3=B8nne=20Petersen?= Date: Fri, 9 Sep 2016 18:50:56 +0200 Subject: [profiler] Remove utils.c/utils.h, move the code to proflog.c/decode.c, and clean it up. * Drop support for fast/null timers. * Use Mono runtime functions for getting the thread ID and allocating buffers. --- man/mprof-report.1 | 16 ---------------- 1 file changed, 16 deletions(-) (limited to 'man') diff --git a/man/mprof-report.1 b/man/mprof-report.1 index c9b756bd990..b96001d2c63 100644 --- a/man/mprof-report.1 +++ b/man/mprof-report.1 @@ -164,13 +164,6 @@ In this case, \f[I]TYPE\f[] can be one of: \f[I]branchmiss\f[]: mispredicted branches .RE .IP \[bu] 2 -\f[I]time=TIMER\f[]: use the TIMER timestamp mode. -TIMER can have the following values: -.RS 2 -.IP \[bu] 2 -\f[I]fast\f[]: a usually faster but possibly more inaccurate timer -.RE -.IP \[bu] 2 \f[I]maxframes=NUM\f[]: when a stack trace needs to be performed, collect \f[I]NUM\f[] frames at the most. The default is 32. @@ -487,15 +480,6 @@ option: especially if the managed heap is big, since every object needs to be inspected. The \f[I]MODE\f[] parameter of the \f[I]heapshot\f[] option can be used to reduce the frequency of the heap shots. -.IP "\f[I]Reduce the timestamp overhead\f[]" 4 -.Sp -On many operating systems or architectures what actually slows down -profiling is the function provided by the system to get timestamp -information. -The \f[I]time=fast\f[] profiler option can be usually used to speed -up this operation, but, depending on the system, time accounting -may have some level of approximation (though statistically the data -should be still fairly valuable). .SS Dealing with the size of the data files .PP When collecting a lot of information about a profiled program, huge -- cgit v1.2.3