Here's an example profile report from admincmd.amxx
Code:
date: Fri Feb 29 01:42:55 2008 map: de_dust
type | name | calls | time / min / max
-------------------------------------------------------------------
n | get_user_flags | 14 | 0.000010 / 0.000000 / 0.000005
n | is_dedicated_server | 14 | 0.000011 / 0.000000 / 0.000002
n | read_argc | 14 | 0.000014 / 0.000000 / 0.000005
n | get_cvar_pointer | 16 | 0.000207 / 0.000001 / 0.000032
n | equal | 14 | 0.000008 / 0.000000 / 0.000001
n | register_plugin | 1 | 0.000027 / 0.000027 / 0.000027
n | register_dictionary | 3 | 0.044636 / 0.001157 / 0.037203
n | register_concmd | 17 | 0.002244 / 0.000088 / 0.000327
n | register_clcmd | 3 | 0.000119 / 0.000034 / 0.000046
n | server_cmd | 14 | 0.000087 / 0.000001 / 0.000032
n | read_argv | 28 | 0.000031 / 0.000000 / 0.000006
n | get_pcvar_flags | 10 | 0.000002 / 0.000000 / 0.000001
n | set_pcvar_flags | 10 | 0.000004 / 0.000000 / 0.000001
p | cmdCvar | 14 | 0.000101 / 0.000001 / 0.000014
p | plugin_cfg | 1 | 0.000020 / 0.000020 / 0.000020
p | plugin_init | 1 | 0.000051 / 0.000051 / 0.000051
f | cmd_access | 14 | 0.000062 / 0.000001 / 0.000015
50 natives, 21 public callbacks, 33 function calls were not executed.
Type "n" is native call, type "p" is public function call from a forward, and type "f" is direct function call.
Note that it doesn't add up recursive calls.
For example: If function a() calls function b(), for the duration that b() is executing, the profiler for function a() is not keeping track of time. As soon as b() stops executing, a() will continue tallying up time.