Performance and Diagnostics hub improvements in Update 2

Performance and Diagnostics hub improvements in Update 2

Rate This
  • Comments 7

MSDN hosts a number of excellent blogs including the .NET Framework Blog. They are not exclusively .NET:

In VS2013 RTM we introduced the Performance and Diagnostics hub with a bunch of tools that help you diagnose issues during your Windows Store app development. With VS2013 Update 2 we added two brand new tools: CPU Usage, and Memory Usage. We also made all the tools in the Performance Diagnostics hub applicable to Windows Phone 8.1 development.

We also enhanced the .NET memory dump analysis feature so you can now inspect values of objects from the dump file.

It's also worth highlighting here the addition of the JSON Debugger Visualizer to Update 2.

You can use the CPU Usage tool in the Performance and Diagnostics hub to see where the CPU is spending time executing C++, C#/VB, and JavaScript code. The tool works on Desktop apps (including console and WPF apps) and Windows Store apps. It can be combined with other tools in the Performance and Diagnostics hub and offers a live CPU graph during collection, fast time range selection, thread filtering, and Just-My-Code. The Memory Usage tool shows (wait for it) memory usage and supports Windows Store and Windows Phone Store apps using C#/VB/C++ and XAML.

Check it out. And check out other developer tools blogs on MSDN.

  • Are any of these with eXpress desktop for C++ or is it pro only?

  • On a separate note; can anyone help us with this issue: github.com/.../22

    We can't figure out the correct switch to squeeze the binary size with VS2013's "nmake".

    Thanks.

  • More precisely we are having trouble sorting out how to update their decade old Makefile.w32 (github.com/.../Makefile.w32), with correct compiler and linker switches; to get best optimizations (and reduce size). It used to be 91KB with previous build in XP (their v1.71) with /O2. Now in Win8.1Update1x64 VS2013 Pro nmake v12.X, with /OX switch; its size is around 300KB.

  • @Adeel

    Are you linking with /mt in your current scenario with nmake? O2 and Ox are really not that different which would justify a 3x increase.

  • @Ankit Asthana, thanks for chipping in. Here is the makefile I am currently using: http://pastebin.com/nhUzfkAB

    I tried with /O1 /mt and the size is 258kb. Its still quite bigger than 90kb!

  • The official binary release version 1.71 is available at http://www.lcdf.org/gifsicle/. Its 90kb in size. Not much code has been changed in v1.83 since 1.71. I am not sure which flags they were using with VC6 compiler (I guess they were using VC6; going by the history of their makefile: github.com/.../Makefile.w32 ... ignoring this week's recent changes).

  • I don't know where else to ask but this is related to Update 2 RC so...

    The C++ editor Navigation Bar is worse in VS 2013 Update 2 RC.

    A third, useless, combobox for Project selection has been added. This only ever has a single entry for all of my projects and takes away space for the other two actually useful combo boxes. Please post about this change (it's not in the release notes page) and please tell us how to hide that first project combo to regain our space.

Page 1 of 1 (7 items)