Skip to content

Releases: microsoft/perfview

PerfView 2.0.23 Public Release

06 Sep 14:48
4915659
Compare
Choose a tag to compare

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.

TraceEvent 2.0.6 Public Release

01 Mar 18:31
9e1ea08
Compare
Choose a tag to compare

Fixed runtime errors trying to load TraceRelogger.dll (which should have been TraceReloggerLib.dll).

TraceEvent 2.0.19 Public Release

13 Jun 21:08
9e1ea08
Compare
Choose a tag to compare
  • Added support for the 'dynamic' keyword to fetch fields from a TraceEvent. (See #630)

Instead of doing

    F(TraceEvent myEvent) {
        Console.WriteLine("MyField = {0}", myEvent.PayloadByName("MyField"));
    }

You can do

    F(TraceEvent myEvent) {
         dynamic dEvent = (dynamic) myEvent;
         Console.WriteLine("MyField = {0}", dEvent.MyField);
    }

It is not any faster, bit it is a bit more convenient.

TraceEvent 2.0.11 Public Release

29 Mar 18:27
9e1ea08
Compare
Choose a tag to compare
  • Fixed a bug where native symbol resolution failed on .NET Core (because CustomMarshalers is not supported there).

PerfView 2.0.15 Public Release

18 May 15:34
952e0bd
Compare
Choose a tag to compare

This is a small bug-fix release of PerfView since the 2.0.12 release. The main interesting feature that was added was support for displaying .NET Core Tiered JIT compilation information (see #679).

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.

PerfView 2.0.12 Public Release

07 Apr 13:48
3741ccc
Compare
Choose a tag to compare

This is a small bug-fix release of PerfView since the 2.0.7 release. No interesting features were added, but small bug fixes were made.

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.

TraceEvent 2.0.10 Public Release

22 Mar 00:44
57c4c99
Compare
Choose a tag to compare
  • Fixed errors trying to load Registry or System.Runtime dlls when running on .NET Desktop and collecting ETW data.
  • Added support for EventPipe Version 3.

PerfView 2.0.7 Public Release

05 Mar 16:11
68a35e7
Compare
Choose a tag to compare

This is a small bug-fix release of PerfView since the 2.0.2 release. No interesting features were added, but small bug fixes were made. Indeed this release is mostly about just working through the mechanics of a second Github release of PerfView.

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.

TraceEvent 2.0.4 Public Release

01 Feb 21:32
Compare
Choose a tag to compare

Adds Support for Version 3 of the EventPipe file format to the library.

TraceEvent 2.0.3 Public Release

29 Jan 19:03
fd07903
Compare
Choose a tag to compare

This is a minor update from the 2.0.2 version.

It contains fixes for problem loading DLLs at runtime (Issue #518 and related).
There were also other minor fixes. See the Github history for more.