I am hearing a lot about these new capabilities of investigating cpu and memory issues using new Diagnostics Tools in Visual Studio 2015 and Intellitrace. Let's say I need to troubleshoot a high memory or cpu problem in a production environment. I know that I can collect iTrace files from the production environment but is it something that could be useful at all to determine cause of high memory/cpu? So far, all uses case I have seen for Intellitrace are related to undesired behavious like exceptions etc but I would like to see any tutorial for using intellitrace for production memory/cpu problems.
It is true that you can use Standalone Collector to record IntelliTrace logs in a production environment. However, these logs will not contain any information about CPU/memory usage (actually iTrace files contain only information about method calls).
It means that if you open iTrace file recorded in the production environment in Visual Studio you will see only the list of recorded diagnostic events and the call tree (if IntelliTrace was configured to collect call information). Diagnostic Tool window will not be available. If you try to open it then the following error message will be reported:
The Diagnostic Tools window does not support the current debugging configuration.
If you want to use Visual Studio 2015 Diagnostic Tools to analyse CPU/Memory usage in production you may be interested in Using the Profiling Tools from Command-line. However, I haven't tried this approach so I don't know if it is convenient. The second problem might be licensing. I'm not sure if these command line tools can be used without installing VS.