This is a small bug-fix release of PerfView since the 2.0.15 release. Here are some of the fixes. Also added a /DotNetCallsSampled option that samples every ~1000 calls, which is infrequent enough that it does not affect perf too badly (more like 10% rather than 100s of %).
- Added the /DotNetCallsSampled command line option that does call instrumentation but samples every 997 calls (to keep overhead low)
- Added the /DisableInlining command line option that tells the runtime not to inline (used with the /DotNetCalls or /DotNetCallsSampled options)
- Minor bug fixes so that things work inside windows docker containers. This works on windowsServerCore Version RS3 or beyond. PerfViewCollect can be used on windowsNano OS
fixed build to support SourceLink for the PerfView/TraceEvent source itself.
- Added docs for using PerfView in windowservercore and nanoserver containers.
Version 2.0.17 5/25/18
- Added support for the ThreadName property that the OS supports. The Thread/SetName event is now parsed well, and if the name is present it shows up in the Stack views.
Version 2.0.16 5/22/18
- Fix bug when parsing 'mixed' EventSources that use both Manifest events and self-describing events in the same EventSource, leading to the self-describing events being parsed as (garbled) manifest events. This can happen when using EventCounters pretty easily since EventCounters use the self-describing format.
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.