xperf 4.0 shipped with Windows Vista SP1/Server 2008 SP1 SDK
xperf 4.1.1
xperf 4.4.6946 shipped with Windows 7 SDK RC
xperf 4.6.7231 shipped with Windows 7 SDK .Net Framework 3.5
xperf 4.8.7701 shipped with the Windows 7 SDK .Net Framework 4.0
xperf 6.2.8229.0 (v.5.x) Windows 8 SDK Consumer Preview (CP) and Windows 8 ADK Consumer Preview (CP).
xperf 6.2.8400.0 (v.5.x) Windows 8 SDK Release Preview (RP) and Windows 8 ADK Release Preview (RP).
xperf 6.2.9200.16834 (v.5.x) Windows 8 SDK RTM and Windows 8 ADK RTM.

If you browse to the main “Windows Performance Analysis Developer Center

http://msdn.microsoft.com/en-us/performance/default.aspx

You might notice that the latest version is:

Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505

You don’t have to install all the SDK, you could just install the Win32 Dev. Tools

Choose custom:

Developer Tools > Windows Development Tools > Win32 Development Tools

c:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\

wpt_ia64.msi

wpt_x64.msi

wpt_x86.msi

Choose the version for your O.S.

Applies to:

Windows XP

Windows Server 2003

Problem description:

After installing the “Microsoft Windows Performance Toolkit”

In All Programs, Microsoft Windows Performance Toolkit you will see:

WPF Performance Suite

WPF Performance Suite Help

 

If you got to a command prompt:

CD \Program Files\Microsoft Windows Performance Toolkit

dir

C:\Program Files\Microsoft Windows Performance Toolkit>dir
Directory of C:\Program Files\Microsoft Windows Performance Toolkit

02/15/2010  09:42 AM    <DIR>          WPF Performance Suite
               0 File(s)              0 bytes
               3 Dir(s)  99,536,506,880 bytes free

You will only see a directory called WPF Performance Suite

CD WPF Performance Suite

dir

C:\Program Files\Microsoft Windows Performance Toolkit\WPF Performance Suite>dir

Directory of C:\Program Files\Microsoft Windows Performance Toolkit\WPF Performance Suite

06/11/2009  05:12 PM            24,576 AspectHelper.dll
04/22/2009  03:11 PM             1,616 AspectMappings.xml
06/11/2009  05:11 PM           190,768 AspectWeaver_x86.dll
02/15/2010  09:42 AM    <DIR>          Demo Applications
06/11/2009  05:12 PM            53,248 EventTrace.dll
06/11/2009  05:11 PM            51,504 milctrl_v0300_x86.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_0.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_1109.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_1453.dll
06/11/2009  05:12 PM            53,248 VisualServices.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_0.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_1109.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_1453.dll
04/29/2009  11:59 PM         3,074,670 WpfPerf.chm
06/11/2009  05:12 PM           790,528 WpfPerf.dll
06/11/2009  05:11 PM            82,184 WpfPerf.exe
06/11/2009  05:11 PM           121,640 WpfPerfHook_x86.dll
06/11/2009  05:12 PM            16,384 WpfPerfService.dll
06/11/2009  05:12 PM           466,944 WpfPerf_managed.exe
              18 File(s)      5,071,694 bytes
               3 Dir(s)  99,535,605,760 bytes free

Cause: 

By Design.

Xperf support for XP
http://blogs.msdn.com/pigscanfly/archive/2008/02/24/xperf-support-for-xp.aspx

Work-around:

Copy the C:\Program Files\Microsoft Windows Performance Toolkit folder from a Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2 based system.

Applies to:

Windows 7 Service Pack 1 (SP1)

Windows 7 RTM

Windows Vista Service Pack 2 (SP2)

Windows Vista Service Pack 1 (SP1)

Windows Vista RTM

For IT administrators, OEM’s and ISV’s, you can read the details from these two whitepapers:

Windows On/Off Transition Performance Analysis

http://msdn.microsoft.com/en-us/windows/hardware/gg463386

Windows On/Off Transitions Solutions Guide

http://msdn.microsoft.com/en-us/windows/hardware/gg463230

The tools that you need to troubleshoot these, is called Windows Performance Toolkit (WPT better known as XPerf and XbootMgr).  The toolkit can be downloaded from:

Windows Performance Analysis Tools

http://msdn.microsoft.com/en-us/performance/cc825801.aspx

Note:  It does require understanding of Windows Internals.

Windows Internals 5th edition by Mark E. Russinovich and David A. Solomon with Alex Ionescu

http://www.microsoft.com/learning/en/us/Book.aspx?ID=12069&locale=en-us

Bootvis on Windows XP, a lot of folks are wondering why the tool was removed from the Microsoft site.

It has been replaced with a much more robust tool called XbootMgr (X Boot Manager) which is a part of the “Windows Performance Toolkit”.

You could find information about the different XbootMgr/XPerf versions here:
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

The little gotcha when trying to install into a Windows XP machine:

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

And two whitepapers from the Product Group (PG) for Vista/Win7 which a good amount still can be used to look into WinXP related boot issues:

How to troubleshoot slow boots (startup) and logons (logins) on your Vista or Windows 7 system.
http://blogs.technet.com/b/yongrhee/archive/2011/06/15/how-to-troubleshoot-slow-boots-startup-and-logons-logins-on-your-vista-or-windows-7-system.aspx

Here is a sample syntax to get you started:

Click on Start, Run, CMD.exe

CD\xperf

Type “Xbootmgr.exe -trace boot” without the quotation marks, and then press Enter.

This will reboot your machine within 5 seconds.

Once the system is back up, login as fast as you can so you won’t skew the results.

Once the logging is done, you should have a boot_1.etl in c:\xperf

Copy the .etl file over to your Windows Vista or Windows 7 for analysis.

Applies to:

Windows Server 2012

Windows 8

Windows Server 2008 R2

Windows 7

Does not work with:

Windows Server 2008

Windows Vista

Windows Server 2003

Windows XP

The Windows Performance Toolkit (WPT) is now shipping as part of the Windows Assessment and Deployment Kit (ADK) for Windows® 8

Click on “Download”

Click on “Next”

Select the radio button for “Yes”

Click on “Next”

Click on “Accept”

Uncheck everything except for “Windows Performance Toolkit”

So it looks like this, and then click on “Install”

Click on “Close”

The installation directory is C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit

If you would like to install WPT on a different system such as one that doesn’t have internet access.  Grab the .msi packages from C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\Redistributables

You will see the following icons:

“Windows Performance Recorder”

“Windows Performance Analyzer”

“GPUView”

So how does WPT 5.0 compare with WPT 4.0?

Related:

XPerf versions
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

XPerf version 4.6 from July 2009
http://blogs.technet.com/b/yongrhee/archive/2009/10/14/xperf-version-4-6-from-july-2009.aspx

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

More information:

Windows Performance Analysis Developer Center
http://msdn.microsoft.com/en-us/performance/cc709422.aspx

Applies to:

Windows Server 2012

Windows 8

Windows Server 2008 R2

Windows 7

In the previous post (Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)), we went thru installing the Windows Performance Toolkit (WPT).

Note:  In Windows Server 2008 R2 and 64-bit Windows 7, you will need to set the following command:

wpr.exe -disablepagingexecutive on

or

go to the registry key to set it on:

HKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

DisablePagingExecutive (dword) 1 (hex)

Restart

What does this do?

“This tells the operating system not to page kernel mode drivers and system code to disk, which is a prerequisite for getting 64-bit call stacks using wpr/wprui/xperf, because 64-bit stack walking depends on metadata in the executable images, and in some situations the wpr/wprui/xperf stack walk code is not allowed to touch paged out pages.”

What if I don’t want to change this setting?

You will not get the detailed information that we (Microsoft) or the 3rd party ISV or 3rd party OEM or your in-house developers need to grab to troubleshoot the issue.

How much extra memory does this consume?

~7MB of nonpaged pool memory.

Does this need to be done in 32-bit Windows 7?  No.

Does this need to be done in Windows Server 2012 or 32-bit/64-bit Windows 8?  No.

Right click on “Windows Performance Recorder”

Click on “Run as administrator”

Click on the drop down “More options”

You will see the following options:

In this example, I’ll be checking the box for “CPU Usage”:

Check the box for “CPU Usage”

Note: If you are troubleshooting a memory leak related issue, you might want to change the “Logging mode:” from Memory to File.

Click on “Start”

Reproduce the issue

Click on “Save”

Under “Type in a detailed description of the problem:”

Type something that provides information of the problem and repro steps.

Next to “File Name:”, select the path that you want to save the file to.

By default, it saves it to %user%\Documents\WPR Files\

Click on “Save”

Wait while the trace is being merged.

Click on “OK”

Click on “Cancel” to stop tracing.

The next step is to analyze the .etl data.

You could use the new “Windows Performance Analyzer” or go back to XperfView.

Related:

Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)
http://blogs.technet.com/b/yongrhee/archive/2012/11/23/installing-the-windows-performance-toolkit-v5-0-wprui-wpr-xperf.aspx

XPerf versions
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

XPerf version 4.6 from July 2009
http://blogs.technet.com/b/yongrhee/archive/2009/10/14/xperf-version-4-6-from-july-2009.aspx

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

More information:

Windows Performance Analysis Developer Center
http://msdn.microsoft.com/en-us/performance/cc709422.aspx

If you browse to the main “Windows Performance Analysis Developer Center

http://msdn.microsoft.com/en-us/performance/default.aspx

You might notice that the latest version is:

Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505

You don’t have to install all the SDK, you could just install the Win32 Dev. Tools

Choose custom:

Developer Tools > Windows Development Tools > Win32 Development Tools

c:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\

wpt_ia64.msi

wpt_x64.msi

wpt_x86.msi

Choose the version for your O.S.

Applies to:

Windows XP

Windows Server 2003

Problem description:

After installing the “Microsoft Windows Performance Toolkit”

In All Programs, Microsoft Windows Performance Toolkit you will see:

WPF Performance Suite

WPF Performance Suite Help

 

If you got to a command prompt:

CD \Program Files\Microsoft Windows Performance Toolkit

dir

C:\Program Files\Microsoft Windows Performance Toolkit>dir
Directory of C:\Program Files\Microsoft Windows Performance Toolkit

02/15/2010  09:42 AM    <DIR>          WPF Performance Suite
               0 File(s)              0 bytes
               3 Dir(s)  99,536,506,880 bytes free

You will only see a directory called WPF Performance Suite

CD WPF Performance Suite

dir

C:\Program Files\Microsoft Windows Performance Toolkit\WPF Performance Suite>dir

Directory of C:\Program Files\Microsoft Windows Performance Toolkit\WPF Performance Suite

06/11/2009  05:12 PM            24,576 AspectHelper.dll
04/22/2009  03:11 PM             1,616 AspectMappings.xml
06/11/2009  05:11 PM           190,768 AspectWeaver_x86.dll
02/15/2010  09:42 AM    <DIR>          Demo Applications
06/11/2009  05:12 PM            53,248 EventTrace.dll
06/11/2009  05:11 PM            51,504 milctrl_v0300_x86.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_0.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_1109.dll
06/11/2009  05:12 PM            36,864 PresentationCoreAspect_3_0_6920_1453.dll
06/11/2009  05:12 PM            53,248 VisualServices.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_0.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_1109.dll
06/11/2009  05:12 PM            11,264 WindowsBaseAspect_3_0_6920_1453.dll
04/29/2009  11:59 PM         3,074,670 WpfPerf.chm
06/11/2009  05:12 PM           790,528 WpfPerf.dll
06/11/2009  05:11 PM            82,184 WpfPerf.exe
06/11/2009  05:11 PM           121,640 WpfPerfHook_x86.dll
06/11/2009  05:12 PM            16,384 WpfPerfService.dll
06/11/2009  05:12 PM           466,944 WpfPerf_managed.exe
              18 File(s)      5,071,694 bytes
               3 Dir(s)  99,535,605,760 bytes free

Cause: 

By Design.

Xperf support for XP
http://blogs.msdn.com/pigscanfly/archive/2008/02/24/xperf-support-for-xp.aspx

Work-around:

Copy the C:\Program Files\Microsoft Windows Performance Toolkit folder from a Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2 based system.

Applies to:

Windows 7 Service Pack 1 (SP1)

Windows 7 RTM

Windows Vista Service Pack 2 (SP2)

Windows Vista Service Pack 1 (SP1)

Windows Vista RTM

For IT administrators, OEM’s and ISV’s, you can read the details from these two whitepapers:

Windows On/Off Transition Performance Analysis

http://msdn.microsoft.com/en-us/windows/hardware/gg463386

Windows On/Off Transitions Solutions Guide

http://msdn.microsoft.com/en-us/windows/hardware/gg463230

The tools that you need to troubleshoot these, is called Windows Performance Toolkit (WPT better known as XPerf and XbootMgr).  The toolkit can be downloaded from:

Windows Performance Analysis Tools

http://msdn.microsoft.com/en-us/performance/cc825801.aspx

Note:  It does require understanding of Windows Internals.

Windows Internals 5th edition by Mark E. Russinovich and David A. Solomon with Alex Ionescu

http://www.microsoft.com/learning/en/us/Book.aspx?ID=12069&locale=en-us

Bootvis on Windows XP, a lot of folks are wondering why the tool was removed from the Microsoft site.

It has been replaced with a much more robust tool called XbootMgr (X Boot Manager) which is a part of the “Windows Performance Toolkit”.

You could find information about the different XbootMgr/XPerf versions here:
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

The little gotcha when trying to install into a Windows XP machine:

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

And two whitepapers from the Product Group (PG) for Vista/Win7 which a good amount still can be used to look into WinXP related boot issues:

How to troubleshoot slow boots (startup) and logons (logins) on your Vista or Windows 7 system.
http://blogs.technet.com/b/yongrhee/archive/2011/06/15/how-to-troubleshoot-slow-boots-startup-and-logons-logins-on-your-vista-or-windows-7-system.aspx

Here is a sample syntax to get you started:

Click on Start, Run, CMD.exe

CD\xperf

Type “Xbootmgr.exe -trace boot” without the quotation marks, and then press Enter.

This will reboot your machine within 5 seconds.

Once the system is back up, login as fast as you can so you won’t skew the results.

Once the logging is done, you should have a boot_1.etl in c:\xperf

Copy the .etl file over to your Windows Vista or Windows 7 for analysis.

Applies to:

Windows Server 2012

Windows 8

Windows Server 2008 R2

Windows 7

Does not work with:

Windows Server 2008

Windows Vista

Windows Server 2003

Windows XP

The Windows Performance Toolkit (WPT) is now shipping as part of the Windows Assessment and Deployment Kit (ADK) for Windows® 8

Click on “Download”

Click on “Next”

Select the radio button for “Yes”

Click on “Next”

Click on “Accept”

Uncheck everything except for “Windows Performance Toolkit”

So it looks like this, and then click on “Install”

Click on “Close”

The installation directory is C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit

If you would like to install WPT on a different system such as one that doesn’t have internet access.  Grab the .msi packages from C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\Redistributables

You will see the following icons:

“Windows Performance Recorder”

“Windows Performance Analyzer”

“GPUView”

So how does WPT 5.0 compare with WPT 4.0?

Related:

XPerf versions
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

XPerf version 4.6 from July 2009
http://blogs.technet.com/b/yongrhee/archive/2009/10/14/xperf-version-4-6-from-july-2009.aspx

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

More information:

Windows Performance Analysis Developer Center
http://msdn.microsoft.com/en-us/performance/cc709422.aspx

Applies to:

Windows Server 2012

Windows 8

Windows Server 2008 R2

Windows 7

In the previous post (Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)), we went thru installing the Windows Performance Toolkit (WPT).

Note:  In Windows Server 2008 R2 and 64-bit Windows 7, you will need to set the following command:

wpr.exe -disablepagingexecutive on

or

go to the registry key to set it on:

HKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

DisablePagingExecutive (dword) 1 (hex)

Restart

What does this do?

“This tells the operating system not to page kernel mode drivers and system code to disk, which is a prerequisite for getting 64-bit call stacks using wpr/wprui/xperf, because 64-bit stack walking depends on metadata in the executable images, and in some situations the wpr/wprui/xperf stack walk code is not allowed to touch paged out pages.”

What if I don’t want to change this setting?

You will not get the detailed information that we (Microsoft) or the 3rd party ISV or 3rd party OEM or your in-house developers need to grab to troubleshoot the issue.

How much extra memory does this consume?

~7MB of nonpaged pool memory.

Does this need to be done in 32-bit Windows 7?  No.

Does this need to be done in Windows Server 2012 or 32-bit/64-bit Windows 8?  No.

Right click on “Windows Performance Recorder”

Click on “Run as administrator”

Click on the drop down “More options”

WARNING: If your Windows Server has equal or more than 64 GB of RAM, please click on “Add Profiles”.

"C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\SampleGeneralProfileForLargeServers.wprp"

Note:  Otherwise, your system count consume a high amount of non-paged pool memory (buffers) causing to instability.

You will see the following options:

In this example, I’ll be checking the box for “CPU Usage”:

Check the box for “CPU Usage”

Note: If you are troubleshooting a memory leak related issue, you might want to change the “Logging mode:” from Memory to File.

Click on “Start”

Reproduce the issue

Click on “Save”

Under “Type in a detailed description of the problem:”

Type something that provides information of the problem and repro steps.

Next to “File Name:”, select the path that you want to save the file to.

By default, it saves it to %user%\Documents\WPR Files\

Click on “Save”

Wait while the trace is being merged.

Click on “OK”

Click on “Cancel” to stop tracing.

The next step is to analyze the .etl data.

You could use the new “Windows Performance Analyzer” or go back to XperfView.

Related:

Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)
http://blogs.technet.com/b/yongrhee/archive/2012/11/23/installing-the-windows-performance-toolkit-v5-0-wprui-wpr-xperf.aspx

XPerf versions
http://blogs.technet.com/b/yongrhee/archive/2009/09/08/xperf-versions.aspx

XPerf version 4.6 from July 2009
http://blogs.technet.com/b/yongrhee/archive/2009/10/14/xperf-version-4-6-from-july-2009.aspx

XP/Server2003:Xperf.exe, XPerfView.exe and XbootMgr.exe missing after installing the WPT (Windows Performance ToolKit)
http://blogs.technet.com/b/yongrhee/archive/2010/02/15/xp-server2003-xperf-exe-xperfview-exe-and-xbootmgr-exe-missing-after-installing-the-wpt-windows-performance-toolkit.aspx

More information:

Windows Performance Analysis Developer Center
http://msdn.microsoft.com/en-us/performance/cc709422.aspx

Applies to:
Windows Server 2012 R2

This post comes courtesy of Carlos Mayol one of my colleagues here in Southern California.

Previously, I had published steps to collect a perfmon using logman locally on a machine which was for a “member server” and/or “guest O.S.”.

Setting a local perfmon in a Windows client or Windows Server.

If you are troubleshooting and/or investigating performance and/or scalability of your 64-bit Hyper-V 2012 R2 / 64-bit Windows Server 2012 R2 running the Hyper-V Role these are performance counters that you should consider.

Setup the two perfmon’s, one short interval and the other one, long interval.

Short-interval:
==========
:: Start a local Perfmon
logman.exe create counter %ComputerName%_short_interval -c “\Cache\*” “\Cluster Resource Control Manager\*” “\Cluster Global Update Manager Messages\*” “\Cluster Network Reconnections(*)\*” “\Cluster Resources(*)\*” “\Cluster NetFt Heartbeats(*)\*” “\Cluster CSV Block Redirection(*)\*” “\Cluster CSV Volume Cache(*)\*” “\Cluster CSV Volume Manager(*)\*” “\Cluster CSV Coordinator(*)\*” “\Cluster CSV File System(*)\*” “\Hyper-V Dynamic Memory Balancer(*)\*” “\ICMP\*” “\ICMPv6\*” “\IPv4\*” “\IPv6\*” “\Hyper-V Dynamic Memory Integration Service\*” “\Hyper-V Dynamic Memory VM(*)\*” “\Hyper-V Hypervisor Logical Processor(*)\*” “\Hyper-V Hypervisor Partition(*)\*” “\Hyper-V Hypervisor Root Partition(*)\*” “\Hyper-V Hypervisor Root Virtual Processor(*)\*” “\Hyper-V Hypervisor Virtual Processor(*)\*” “\Hyper-V Hypervisor\*” “\Hyper-V Legacy Network Adapter(*)\*” “\Hyper-V Replica VM(*)\*” “\Hyper-V Shared VHDX(*)\*” “\Hyper-V Virtual IDE Controller (Emulated)(*)\*” “\Hyper-V Virtual Machine Bus\*” “\Hyper-V Virtual Machine Health Summary\*” “\Hyper-V Virtual Network Adapter(*)\*” “\Hyper-V Virtual Storage Device(*)\*” “\Hyper-V Virtual Switch Port(*)\*” “\Hyper-V Virtual Switch Processor(*)\*” “\Hyper-V Virtual Switch(*)\*” “\Hyper-V VM Live Migration(*)\*” “\Hyper-V VM Remoting(*)\*” “\Hyper-V VM Save, Snapshot, and Restore(*)\*” “\Hyper-V VM Vid Numa Node(*)\*” “\LogicalDisk(*)\*” “\Memory\*” “\Netlogon\*” “\Network Interface(*)\*” “\Network Inspection System\*” “\NUMA Node Memory(*)\*” “\Paging File(*)\*” “\Per Processor Network Activity Cycles(*)\*” “\Per Processor Network Interface Card Activity(*)\*” “\PhysicalDisk(*)\*” “\Physical Network Interface Card Activity(*)\*” “\Process(*)\*” “\Processor(*)\*” “\Processor Information(*)\*” “\RDMA Activity(*)\*” “\Redirector\*” “\RemoteFX Network(*)\*” “\RemoteFX Root GPU Management(*)\*” “\SMB Client Shares\*” “\SMB Server Shares(*)\*” “\SMB Server Sessions\*” “\Server\*” “\Server Work Queues(*)\*” “\System\*” “\TCPv4\*” “\TCPv6\*” -f bincirc -v mmddhhmm -max 500 -si 00:00:02

logman.exe start %ComputerName%_short_interval

Note:  I personally like to capture all the counters and instances.  The reason is, I cannot tell you how many times, where I was looking at a perfmon, that I went, ok, the bread crumbs lead this way, let me look at that counter, just to find out, it wasn’t collected.  And then having to wait for the problem to reoccur.

::Stop perfmon

logman.exe stop %ComputerName%_short_interval

Long-interval:
=========
:: Start a local Perfmon
logman.exe create counter %ComputerName%_long_interval  -c “\Cache\*” “\Cluster Resource Control Manager\*” “\Cluster Global Update Manager Messages\*” “\Cluster Network Reconnections(*)\*” “\Cluster Resources(*)\*” “\Cluster NetFt Heartbeats(*)\*” “\Cluster CSV Block Redirection(*)\*” “\Cluster CSV Volume Cache(*)\*” “\Cluster CSV Volume Manager(*)\*” “\Cluster CSV Coordinator(*)\*” “\Cluster CSV File System(*)\*” “\Hyper-V Dynamic Memory Balancer(*)\*” “\ICMP\*” “\ICMPv6\*” “\IPv4\*” “\IPv6\*” “\Hyper-V Dynamic Memory Integration Service\*” “\Hyper-V Dynamic Memory VM(*)\*” “\Hyper-V Hypervisor Logical Processor(*)\*” “\Hyper-V Hypervisor Partition(*)\*” “\Hyper-V Hypervisor Root Partition(*)\*” “\Hyper-V Hypervisor Root Virtual Processor(*)\*” “\Hyper-V Hypervisor Virtual Processor(*)\*” “\Hyper-V Hypervisor\*” “\Hyper-V Legacy Network Adapter(*)\*” “\Hyper-V Replica VM(*)\*” “\Hyper-V Shared VHDX(*)\*” “\Hyper-V Virtual IDE Controller (Emulated)(*)\*” “\Hyper-V Virtual Machine Bus\*” “\Hyper-V Virtual Machine Health Summary\*” “\Hyper-V Virtual Network Adapter(*)\*” “\Hyper-V Virtual Storage Device(*)\*” “\Hyper-V Virtual Switch Port(*)\*” “\Hyper-V Virtual Switch Processor(*)\*” “\Hyper-V Virtual Switch(*)\*” “\Hyper-V VM Live Migration(*)\*” “\Hyper-V VM Remoting(*)\*” “\Hyper-V VM Save, Snapshot, and Restore(*)\*” “\Hyper-V VM Vid Numa Node(*)\*” “\LogicalDisk(*)\*” “\Memory\*” “\Netlogon\*” “\Network Interface(*)\*” “\Network Inspection System\*” “\NUMA Node Memory(*)\*” “\Paging File(*)\*” “\Per Processor Network Activity Cycles(*)\*” “\Per Processor Network Interface Card Activity(*)\*” “\PhysicalDisk(*)\*” “\Physical Network Interface Card Activity(*)\*” “\Process(*)\*” “\Processor(*)\*” “\Processor Information(*)\*” “\RDMA Activity(*)\*” “\Redirector\*” “\RemoteFX Network(*)\*” “\RemoteFX Root GPU Management(*)\*” “\SMB Client Shares\*” “\SMB Server Shares(*)\*” “\SMB Server Sessions\*” “\Server\*” “\Server Work Queues(*)\*” “\System\*” “\TCPv4\*” “\TCPv6\*” -f bincirc -v mmddhhmm -max 500 -si 00:05:00

logman.exe start %ComputerName%_long_interval

Note:  I personally like to capture all the counters and instances.  The reason is, I cannot tell you how many times, where I was looking at a perfmon, that I went, ok, the bread crumbs lead this way, let me look at that counter, just to find out, it wasn’t collected.  And then having to wait for the problem to reoccur.

Note 2:  You could change the interval for the long from to -si 00:05:00 to anything depending on how long you want to capture.  For more info on the sample interval that you need to choose, check out:  How often should Perfmon Sample?

::Stop perfmon

logman.exe stop %ComputerName%_long_interval

More information:
============
The three (3) ways of setting up a perfmon log

*  If you use my colleague Clint Huffman’s Performance Analysis of Logs (PAL), the “Hyper-V” performance is named “Microsoft Windows Server 2012 Hyper-V”.

How to setup an in-flight recorder:
•How To Equip Your Windows Server Environment With A Blackbox Flight Recorder
or
•How to create a “black box” performance counter data collector
or
•Put a BlackBox (Black Box) on your server!

Applies to:

Windows Server 2012 R2

Hyper-V 2012 R2

If you are troubleshooting an iSCSI storage problem, then these are the data that you should consider collecting.

The first item to consider is:

Using file copy to measure storage performance – Why it’s not a good idea and what you should do instead
https://blogs.technet.microsoft.com/josebda/2014/08/18/using-file-copy-to-measure-storage-performance-why-its-not-a-good-idea-and-what-you-should-do-instead/

#2) Setup a perfmon

Setting a local perfmon in a Windows client or Windows Server.
https://blogs.technet.microsoft.com/yongrhee/2015/05/16/setting-a-local-perfmon-in-a-windows-client-or-windows-server/
or

Setting a local perfmon in 64-bit Hyper-V 2012 R2 and/or 64-bit Windows Server 2012 R2 Hyper-V.
https://blogs.technet.microsoft.com/yongrhee/2016/11/19/setting-a-local-perfmon-in-64-bit-hyper-v-2012-r2-andor-64-bit-windows-server-2012-r2-hyper-v/

#3) Setup a network trace

Network tracing (packet sniffing) built-in to Windows and Windows Server.
https://blogs.technet.microsoft.com/yongrhee/2012/12/01/network-tracing-packet-sniffing-built-in-to-windows-server-2008-r2-and-windows-server-2012/

or

:: Start Network tracing (a.k.a. sniffing) tracing on Hyper-V 2012 R2 or Windows Server 2012 R2 Hyper-V
netsh.exe trace start scenario=AddressAcquisition,LAN,NDIS,NetConnection,Virtualization capture=yes capturetype=both report=yes persistent=no maxSize=4096 fileMode=circular correlation=no perfMerge=yes overwrite=yes traceFile=c:\Temp\NetTrace.etl

#4) Installing the tools for ETW tracing:

Download the latest Windows 10 SDK

Download: Windows 10 Software Development Kit (SDK)
https://blogs.technet.microsoft.com/yongrhee/2015/08/11/download-windows-10-software-development-kit-sdk/

and then install just the “Windows Performance Toolkit”

WPT: Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)
https://blogs.technet.microsoft.com/yongrhee/2012/11/23/wpt-installing-the-windows-performance-toolkit-v5-0-wprui-wpr-xperf/

Note:  Just be aware that the screen shots showcase the Windows 8.1 SDK, but you want the Windows 10 SDK.

#5)  Setting up and starting the ETW tracing:

:: Start Kernel tracing and MiniFilter tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -on PROC_THREAD+LOADER+FileIO+DISPATCHER+CSWITCH+DISK_IO_INIT+PROFILE+FILENAME+DRIVERS+NETWORKTRACE+DPC+INTERRUPT+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE -stackwalk CSwitch+ReadyThread+DiskReadInit+DiskWriteInit+DiskFlushInit+FileCreate+FileCleanup+FileClose+FileRead+FileWrite+FileFlush+MiniFilterPreOpInit+MiniFilterPostOpInit -f c:\temp\Pre_Kernel.etl -BufferSize  1024 -MinBuffers 1024 -MaxBuffers 1024 -MaxFile 4096 -FileMode Circular

::Start iSCSI tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start iSCSITrace -on msiscsi_iScsi:0xffffffffffffffff:0xffffffff:’stack’+1babefb4-59cb-49e5-9698-fd38ac830a91:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_iSCSITrace.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start MPIOtracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start MPIOTrace -on 8E9AC05F-13FD-4507-85CD-B47ADC105FF6:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_MPIOTrace.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start DSM tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start DSMTrace -on DEDADFF5-F99F-4600-B8C9-2D4D9B806B5B:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_DSMTrace.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start Storport tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start Storport -on Microsoft-Windows-StorPort:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_Storport.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start StoragePerformance tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start StoragePerformance  -on A103CABD-8242-4A93-8DF5-1CDF3B3F26A6:0xffffffffffffffff:0xffffffff:’stack’+F5D05B38-80A6-4653-825D-C414E4AB3C68:0xffffffffffffffff:0xffffffff:’stack’+6B4DB0BC-9A3D-467D-81B9-A84C6F2F3D40:0xffffffffffffffff:0xffffffff:’stack’+C4636A1E-7986-4646-BF10-7BC3B4A76E8E:0xffffffffffffffff:0xffffffff:’stack’+CB587AD1-CC35-4EF1-AD93-36CC82A2D319:0xffffffffffffffff:0xffffffff:’stack’+cc7b00d3-75c9-42cc-ae56-bf6d66a9d15d:0xffffffffffffffff:0xffffffff:’stack’+90742496-54a9-4075-8079-425399080068:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_Storage_Performance.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start Microsoft-Windows-TCPIP tracing
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start TCPIP -on Microsoft-Windows-TCPIP:0xffffffffffffffff:0xffffffff:’stack’ -f c:\temp\Pre_TCPIP.etl -BufferSize 512 -MinBuffers 320 -MaxBuffers 320 -MaxFile 4096 -FileMode Circular

::Start Hyper-V
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -start Hyper-V -on BB510E5F-2EB9-491A-81E4-F04654388F2B:0xffffffffffffffff:0xffffffff:’stack’+67E605EE-A4D8-4C46-AE50-893F31E13963:0xffffffffffffffff:0xffffffff:’stack’+67DC0D66-3695-47C0-9642-33F76F7BD7AD:0xffffffffffffffff:0xffffffff:’stack’+F2E2CE31-0E8A-4E46-A03B-2E0FE97E93C2:0xffffffffffffffff:0xffffffff:’stack’+29F239D9-979B-4160-A7DD-C4EA36A75181:0xffffffffffffffff:0xffffffff:’stack’+EEBBE72A-286C-4CCD-BBAD-88957BF388C4:0xffffffffffffffff:0xffffffff:’stack’+90742496-54A9-4075-8079-425399080068:0xffffffffffffffff:0xffffffff:’stack’+177D1599-9764-4E3A-BF9A-C86887AADDCE:0xffffffffffffffff:0xffffffff:’stack’+7B0EA079-E3BC-424A-B2F0-E3D8478D204B:0xffffffffffffffff:0xffffffff:’stack’ -BufferSize 1024 -MinBuffers 1024 -MaxBuffers 1024 -f c:\temp\Pre_Hyper-V.etl

::The Hyper-V is optional, add it if you have the Hyper-V role installed.

#6)  Reproduce the issue

::<repro>
Timeout.exe /t 300

Note:  300 is in seconds.  300 seconds is 5 minutes.

Note 2:  Press Enter to stop

#7)  Stop the ETW traces:

::Stop all the iSCSI and Storage related traces
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -stop -stop iSCSITrace -stop DSMTrace -stop MPIOTrace -stop Storport -stop StoragePerformance -stop TCPIP -stop Hyper-V -d c:\temp\Pre_iSCSI_Disk_Troubleshooting.etl

::Stop Network tracing tracing
netsh.exe trace stop

::Merge the WPP (Classic) based ETW traces
“C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\Xperf.exe” -merge c:\temp\Pre_iSCSITrace.etl c:\temp\Pre_MPIOTrace.etl c:\temp\Pre_DSMTrace.etl c:\temp\Pre_Hyper-V.etl c:\temp\Pre_iSCSI_Disk_Troubleshooting.etl c:\temp\iSCSI_Classic-WPP_ETW.etl

:: Stop the perfmon logs

logman.exe stop %ComputerName%_long_interval
logman.exe stop %ComputerName%_short_interval

#8)  Analyzing the data:

Measuring Disk Latency with Windows Performance Monitor (Perfmon)
https://blogs.technet.microsoft.com/askcore/2012/02/07/measuring-disk-latency-with-windows-performance-monitor-perfmon/

Hyper-V Performance – Storage
https://blogs.technet.microsoft.com/neales/2016/11/07/hyper-v-performance-storage/

Disk Performance Internals
https://blogs.technet.microsoft.com/supportingwindows/2014/12/09/disk-performance-internals/

Deciphering Storport Traces 101
https://blogs.technet.microsoft.com/askcore/2014/08/19/deciphering-storport-traces-101/

Register Here