PerfView Version 1.9 Released to the Web

Today I have updated the PerfView Download Site, to version 1.9 of the program.   In particular this version has a fix for a symbol resolution on data collected from older (e.g. Win7 OSes) machine that I mentioned in a previous blog post.    It also has a number of other notable features

• Generalization of Thread Time views support arbitrary requests demarked by user defined Start-Stop events
• Significantly improved support for Async and Parallel activities in the 'Thread Time' Views
• Can display file disk usage in the stack view using the Size -> DirectorySize option
• Supports reading a very simple *.PerfView.XML or *.PerfView.JSON file, which enable reading data from 'foreign' profilers.
• Support for Windows 10 self describing ETW events
• Support for EventSource causality tracking
• Support for V4.6.2 .NET Runtimes that line number level on NGEN images (e.g. the framework) even if IL PDBS are not available when NGEN images were created

Some of these features need a bit of a 'walk through' to show how useful they are, so I will be blogging about that in the days and weeks ahead.  

In particular you can now view data that was collected on a Linux machine or consume data from other 'foreign' profilers (or other hierarchical data sources).  

If you are new to PerfView the easiest way to get going is to simply download it (you are only a few clicks away).   Or for the less adventurous, you can watch some of the PerfView videos on channel 9.  

Vance

Comments

• Anonymous
  February 21, 2016
  The comment has been removed

• Anonymous
  February 21, 2016
  The comment has been removed

• Anonymous
  March 12, 2016
  The comment has been removed

• Anonymous
  March 12, 2016
  @Fabio use the NuGet Version: www.nuget.org/.../Microsoft.Diagnostics.Tracing.EventSource

• Anonymous
  March 14, 2016
  @Fabio.  Please don't use the Nuget package on UWP apps as Andre advised.  UWP already has the latest, and your app will simply be bigger and slower (and there are possible sublte bugs since we don't test that configuration).   Buyt to answer your question, yes, EventSource exists in the .NET RUntime used by UWP apps (System.Diagnostics.Tracing.EventSource).   However it sounds like you are trying to extend it using native code (C++?).   That does not work (as you found out).  It has nothing to do with EventSource per-se,. EventSource is really for when you are in C# or VB.  For native languages the suggestion is to use TraceLogging (see msdn.microsoft.com/.../dn904636(v=vs.85).aspx)

  • Anonymous
    March 20, 2016
    ok, thanks. I never coded an UWP app, so I was not aware of it.

• Anonymous
  March 15, 2016
  @Vance Morrison Thanks for the link. I understood my error. @Andre.Ziegler Thanks for sugestion

• Anonymous
  March 17, 2016
  Hi, not sure where to report bugs, so I'm pasting it here: https://social.msdn.microsoft.com/Forums/exchange/en-us/b177d1db-553b-464c-be4d-2f6dd3a746fc/perfview-bug-when-selecting-time-range?forum=wptk_v4 It's bug about selected time range. Quite annoying when working a lot with time ranges because it resets quite often. Any possibility to fix it in future version(s)?

• Anonymous
  March 21, 2016
  Hi Vance,I use the following command to collect GC events:perfview /GCCollectOnly /NoNGenRundown /AcceptEULA /nogui /MaxCollectSec:600 collectCould you please suggest how to add stacktraces for GC event while keeping the size of the trace relatively small.Thank you.

• Anonymous
  March 22, 2016
  The comment has been removed

• Anonymous
  April 19, 2016
  On the PerfView 1.9 download page, the Additional Information section says "For questions and/or discussion please visit the CLR Developer Tools Forum". However, MSDN Forums nowadays classifies that forum (netfxtoolsdev) under "Archived Forums A-B", and the most recent post is from January 2013. Is the advice on the download page still valid or should some other forum be used instead?

• Anonymous
  April 20, 2016
  Any chance of getting -InMemoryCircularBuffer working in Win7 / 2008R2 ?Is it even possible with win 6.1 ETW infrastructure? (I've not tested WPR yet)I'm getting this in win7 :[EXECUTING: PerfView collect /nogui -InMemoryCircularBuffer -MaxCollectSec:5]...Error stopping Kernel session: System Tracing is only supported on Windows 8 and above.Aborting tracing for sessions 'NT Kernel Logger' and 'PerfViewSession'.Strange, it tries to stop and yet it never logged a start like it does when you do not try to use a memory circular buffer :[Kernel Log: C:\bin\PerfView\PerfViewData.kernel.etl][User mode Log: C:\bin\PerfView\PerfViewData.etl]The point is to use it in win7 / 2008R2 in "in memory" flight recorder mode so as to not use disk at all in the first part of the capture (of course after stop it it must save to disk).

  • Anonymous
    April 23, 2016
    I've tested WPRUI ( from ADK 8.1) in Win7 and it works with in memory circular buffer, so I don't think it needs windows 8 for that. Why PerfView does ?

• Anonymous
  June 12, 2016
  Hi Vance, Thanks for your perfview tool, it's very helpful for my performance tuning work. but I found the version 1.9 will throw System.IO.IOException when wrote etl to zip file. the logs as follows:*** NGEN CREATEPDB returns: 0Found NGEN pdb d:\Users\JOE\AppData\Local\Temp\symbols\System.Core.ni.pdb\cc5a18de56b1ba18426a9607afab2be21\System.Core.ni.pdbFound NGEN pdb d:\Users\JOE\AppData\Local\Temp\symbols\System.ni.pdb\9a2715c05cb7bc5d06a7cc5801c474ca1\System.ni.pdbFound NGEN pdb d:\Users\JOE\AppData\Local\Temp\symbols\mscorlib.ni.pdbb312f3f14daccc8bdc79fdcd75a45e21\mscorlib.ni.pdbFound NGEN pdb d:\Users\JOE\AppData\Local\Temp\symbols\System.Net.Http.ni.pdb\c2a2e2c6297c71a9d5ea51e48a65d1de1\System.Net.Http.ni.pdbGenerating NGEN Pdbs took 36.1 secMoving \perf\test2.etl.new to \perf\test2.etlDeleting temp fileMerge took 38.287 sec.Merge output file \perf\test2.etl[Zipping ETL file \perf\test2.etl][Writing 13 PDBS to Zip file]

• Anonymous
  June 16, 2016
  The comment has been removed

• Anonymous
  August 10, 2016
  the download link is broken :-(