Windows 在xperf输出中使用机器模式进行自定义实用程序的进一步解析有什么实质性的好处吗?

Windows 在xperf输出中使用机器模式进行自定义实用程序的进一步解析有什么实质性的好处吗?,windows,xperf,wpr,Windows,Xperf,Wpr,所以我试着处理用WPR记录的性能数据,并用xperf处理成.csv格式,它有两种模式,-目标人模式和-目标机器模式,我可以看出区别在于机器模式似乎将来自同一时间戳的事件分组成一行或两行,但是,当使用自定义外部实用程序来解析这些数据时,这真的有好处吗 我可以看到机器版本中的信息可能会少一点 人类模式 Microsoft-Windows-DotNETRuntime/CLRMethod/MethodUnloadVerbose, 12535888, wpa.exe (8020),

所以我试着处理用WPR记录的性能数据,并用xperf处理成.csv格式,它有两种模式,-目标人模式和-目标机器模式,我可以看出区别在于机器模式似乎将来自同一时间戳的事件分组成一行或两行,但是,当使用自定义外部实用程序来解析这些数据时,这真的有好处吗

我可以看到机器版本中的信息可能会少一点

人类模式

Microsoft-Windows-DotNETRuntime/CLRMethod/MethodUnloadVerbose,   12535888,          wpa.exe (8020),      11056,   3, , , , , 0x00007ffc4123c3f0, 0x00007ffc3f89ce80, 0x00007ffc40f09f30, 0x00000021, 0x0600067f, 8, "MS.Internal.IO.Zip.ZipIOCentralDirectoryFileHeader", "get_OffsetOfLocalHeader", "instance int64  ()", 6
Microsoft-Windows-RPC/RpcServerCall/win:Stop,   12535888,      svchost.exe (1100),       1912,   2, {e9934bb1-c880-48b5-a31b-5a99a27faade}, , , , 0x00000000
                  Stack,   12535888,       1912,   1, 0x00007ffcb01a5a04,        ntdll.dll!0x00007ffcb01a5a04
                  Stack,   12535888,       1912,   2, 0x00007ffcb016022c,        ntdll.dll!0x00007ffcb016022c
                  Stack,   12535888,       1912,   3, 0x00007ffcb0160059,        ntdll.dll!0x00007ffcb0160059
                  Stack,   12535888,       1912,   4, 0x00007ffcafe459ae,       rpcrt4.dll!0x00007ffcafe459ae
                  Stack,   12535888,       1912,   5, 0x00007ffcafe59c7a,       rpcrt4.dll!0x00007ffcafe59c7a
                  Stack,   12535888,       1912,   6, 0x00007ffcafdfa09c,       rpcrt4.dll!0x00007ffcafdfa09c
                  Stack,   12535888,       1912,   7, 0x00007ffcafe1438c,       rpcrt4.dll!0x00007ffcafe1438c
                  Stack,   12535888,       1912,   8, 0x00007ffcafe15beb,       rpcrt4.dll!0x00007ffcafe15beb
                  Stack,   12535888,       1912,   9, 0x00007ffcafe086ea,       rpcrt4.dll!0x00007ffcafe086ea
                  Stack,   12535888,       1912,  10, 0x00007ffcb01325fe,        ntdll.dll!0x00007ffcb01325fe
                  Stack,   12535888,       1912,  11, 0x00007ffcb01330d9,        ntdll.dll!0x00007ffcb01330d9
                  Stack,   12535888,       1912,  12, 0x00007ffcaff08364,     kernel32.dll!0x00007ffcaff08364
                  Stack,   12535888,       1912,  13, 0x00007ffcb0165e91,        ntdll.dll!0x00007ffcb0165e91
机器模式:

Microsoft-Windows-DotNETRuntime/CLRMethod/MethodUnloadVerbose,   12535888,          wpa.exe (8020),      11056,   3, , , , , 0x00007ffc4123c3f0, 0x00007ffc3f89ce80, 0x00007ffc40f09f30, 0x00000021, 0x0600067f, 8, "MS.Internal.IO.Zip.ZipIOCentralDirectoryFileHeader", "get_OffsetOfLocalHeader", "instance int64  ()", 6
Microsoft-Windows-RPC/RpcServerCall/win:Stop,   12535888,      svchost.exe (1100),       1912,   2, {e9934bb1-c880-48b5-a31b-5a99a27faade}, , , , 0x00000000
                  Stack,   12535888,       1912, ntdll.dll!0x00007ffcb01a5a04, ntdll.dll!0x00007ffcb016022c, ntdll.dll!0x00007ffcb0160059, rpcrt4.dll!0x00007ffcafe459ae, rpcrt4.dll!0x00007ffcafe59c7a, rpcrt4.dll!0x00007ffcafdfa09c, rpcrt4.dll!0x00007ffcafe1438c, rpcrt4.dll!0x00007ffcafe15beb, rpcrt4.dll!0x00007ffcafe086ea, ntdll.dll!0x00007ffcb01325fe, ntdll.dll!0x00007ffcb01330d9, kernel32.dll!0x00007ffcaff08364, ntdll.dll!0x00007ffcb0165e91