Although using paged memory can slow event logger performance, it can also
enhance system performance as a whole.
Not all of the command line switches work with all of the verbs. You need to know which command
line switches to use with each verb. With that requirement in mind, here are a few LogMan
examples.
LogMan create counter perf_log -c ???\Processor(_Total)\% Processor Time???
LogMan create trace trace_log -nb 16 256 -bs 64 -o c:\logfile
LogMan start perf_log
LogMan update perf_log -si 10 -f csv -v mmddhhmm
LogMan update trace_log -p ???Windows Kernel Trace??? (disk,net)
Viewing the Results of Changes with the PerfMon Utility
PerfMon was the performance monitoring utility of the past. Windows 2000 represents a sort of
transition point where you can use PerfMon or the Performance console. However, starting with
Windows XP, the Performance console is the main event and PerfMon has taken a background role.
Now all that this utility does for you is open the Performance counter with settings that you saved
from Windows NT 4.0. In other words, you can see the same counters as you did in Windows NT
4.0, but the application displaying them differs.
Pages:
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092