Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mlprof(1) [debian man page]

mlprof(1)						      General Commands Manual							 mlprof(1)

NAME
mlprof - display profiling information for a MLton-compiled executable SYNOPSIS
mlprof [option ...] a.out [mlmon.out ...] DESCRIPTION
mlprof extracts information from an executable compiled by MLton with -profile alloc or -profile time and the resulting mlmon.out file pro- duced by running the executable. The output of mlprof consists of an initial line indicating the total amount of CPU time or bytes allocated. After this, source functions are listed along with the percentage of this total that they used, in decreasing order. If the program was compiled with -profile-stack true, mlprof will display the time spent or bytes allocated while the function was on the stack and in GC in addition to the time or bytes that the function is directly responsible for. With multiple mlmon.out files, mlprof will sum the profiling information. OPTIONS
-call-graph file Write a call graph containing the table data to a dot file. See the MLton User Guide for details. -graph-title string Set the call-graph title. -gray {false|true} Gray call-graph nodes according to stack %. This only makes sense if the executable was compiled -profile-stack true. -keep exp Only show functions specified by exp. For details on the allowed expressions, see the MLton User Guide. Multiple -keep expressions are not allowed. -mlmon file Process the list of whitespace-separated mlmon.out files found in the specified file. -raw {false|true} Show the raw counts in addition to the percentages. -show-line {false|true} Show the file and line for each function. -split regexp Treat duplicates of functions whose name matches regexp as different functions. -thresh x An abbreviation for -keep '(thresh x)', which only prints information about functions whose percentage is greater than or equal to x, where 0 <= x <= 100.0. -tolerant {false|true} Print a warning about broken mlmon.out files, but do not exit. SEE ALSO
mlton(1) and the MLton Guide. June 8, 2010 mlprof(1)

Check Out this Related Man Page

MONCONTROL(3)						   BSD Library Functions Manual 					     MONCONTROL(3)

NAME
moncontrol, monstartup -- control execution profile LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
moncontrol(int mode); monstartup(u_long *lowpc, u_long *highpc); DESCRIPTION
An executable program compiled using the -pg option to cc(1) automatically includes calls to collect statistics for the gprof(1) call-graph execution profiler. In typical operation, profiling begins at program startup and ends when the program calls exit. When the program exits, the profiling data are written to the file gmon.out, then gprof(1) can be used to examine the results. moncontrol() selectively controls profiling within a program. When the program starts, profiling begins. To stop the collection of his- togram ticks and call counts use moncontrol(0); to resume the collection of histogram ticks and call counts use moncontrol(1). This feature allows the cost of particular operations to be measured. Note that an output file will be produced on program exit regardless of the state of moncontrol(). Programs that are not loaded with -pg may selectively collect profiling statistics by calling monstartup() with the range of addresses to be profiled. lowpc and highpc specify the address range that is to be sampled; the lowest address sampled is that of lowpc and the highest is just below highpc. Only functions in that range that have been compiled with the -pg option to cc(1) will appear in the call graph part of the output; however, all functions in that address range will have their execution time measured. Profiling begins on return from monstartup(). ENVIRONMENT
PROFDIR Directory to place the output file(s) in. When this is set, instead of writing the profiling output to gmon.out, a filename is gen- erated from the process id and name of the program (e.g., 123.a.out). If you are profiling a program that forks, or otherwise cre- ates multiple copies, setting this is the only reasonable way to get all profiling data. FILES
gmon.out execution data file SEE ALSO
cc(1), gprof(1), profil(2) BSD
June 4, 1993 BSD
Man Page