Merge pull request #3860 from Microsoft/mrtk_development

Visual Profiler docs from mrtk_development -> stabilization

Author: keveleigh

Documentation/Diagnostics/ConfiguringDiagnostics.md

@@ -46,4 +46,4 @@ The speed at which to move the profiler window to maintain visibility within the
 ## See Also
 
 - [Diagnostics System](DiagnosticsSystemGettingStarted.md)
-- [Using the Visual Profiler](../TODO.md)
+- [Using the Visual Profiler](UsingVisualProfiler.md)

Documentation/Diagnostics/DiagnosticsSystemGettingStarted.md

@@ -59,5 +59,5 @@ accurately reflect actual application performance when run from within the edito
 
 - [Diagnostics API documentation](xref:Microsoft.MixedReality.Toolkit.Diagnostics)
 - [Configuring the Diagnostics System](ConfiguringDiagnostics.md)
-- [Using the Visual Profiler](../TODO.md)
+- [Using the Visual Profiler](UsingVisualProfiler.md)
 

Documentation/Diagnostics/UsingVisualProfiler.md

@@ -1,6 +1,64 @@
 # Using the Visual Profiler
 
-<< >>
+The VisualProfiler provides an easy to use, in application view of a mixed reality application's performance. The profiler is supported on all Mixed Reality Toolkit platforms, including:
+
+- Microsoft HoloLens
+- Microsoft HoloLens 2
+- Windows Mixed Reality Immersive headsets
+- OpenVR
+
+While developing an application, be sure to focus on multiple parts of the scene as the Visual Profiler displays data relative to the current view. 
+
+> Focus attention on portions of the scene with complex objects, particle effects or activity. These and other factors often contribute to reduction in application performance and a less than ideal user experience.
+
+## Visual Profiler Interface
+
+![Visual Profiler Interface](../../External/ReadMeImages/Diagnostics/VisualProfiler.png)
+
+The Visual Profiler interface includes the following components:
+
+- [Frame Rate](#frame-rate)
+- [Frame Time](#frame-time)
+- [Frame Graph](#frame-graph)
+- [Memory Utilization](#memory-utilization)
+
+### Frame Rate
+
+In the upper left corner of the interface is the frame rate, measured in frames per second. For the best user experience and comfort, this value should be as high as possible. 
+
+The specific platform and hardware configuration will play a significant role in the maximum achievable frame rate. Some common target values include:
+
+- Microsoft HoloLens: 60
+- Windows Mixed Reality Ultra: 90
+
+### Frame Time
+
+To the right of the frame rate is the frame time, in milliseconds, spent on the CPU. To achieve the target frame rates mentioned previously, an application can spend the following amount of time per frame:
+
+- 60 fps: 16.6 ms
+- 90 fps: 11.1 ms
+
+> GPU time is planned to be added in a future release.
+
+### Frame Graph
+
+The frame graph provides a graphical display of the application frame rate history.
+
+![Visual Profiler Frame Graph](../../External/ReadMeImages/Diagnostics/VisualProfilerMissedFrames.png)
+
+> When using the application, look for missed frames. Missed frames indicate the application is not hitting its target frame rate and may need optimization work.
+
+### Memory Utilization
+
+The memory utilization display allows for easy understanding of how the current view is impacting an application's memory consumption. 
+
+![Visual Profiler Frame Graph](../../External/ReadMeImages/Diagnostics/VisualProfilerMemory.png)
+
+> When using application, look for total memory usage. Key indicators include: nearing the memory limit and rapid changes in usage.
+
+## Customizing the Visual Profiler
+
+The Visual Profiler's appearance and behavior are customizable via the diagnostics system profile. Please see [Configuring the Diagnostics System](ConfiguringDiagnostics.md) for more information.
 
 ## See Also
 

Documentation/toc.yml

@@ -90,7 +90,7 @@
       - name: Configuring the Diagnostics System
         href: Diagnostics/ConfiguringDiagnostics.md
       - name: Using the Visual Profiler
-        href: TODO.md
+        href: Diagnostics/UsingVisualProfiler.md
   - name: Other Features
     items:
     - name: QR Tracking