Frame rate counters in Windows Phone Emulator
September 30, 2013
Applies to: Windows Phone 8 | Windows Phone OS 7.1
When you run an app in Windows Phone Emulator, you can use the frame rate counters to monitor the performance of your app. The following illustration shows the frame rate counters.
This topic contains the following sections.
The following table describes each frame rate counter. For information about the recommended ranges of values for individual frame rate counters, see the section “Identifying Performance Issues for Graphics-Intensive Applications” in the topic App performance considerations for Windows Phone.
Frame rate counter
Composition (Render) Thread Frame Rate (FPS)
The rate at which the screen is updated.
User Interface Thread Frame Rate (FPS)
The rate at which the UI thread is running.
Texture Memory Usage
The video memory and system memory copies of textures being used in the app.
The number of explicit surfaces being passed to the GPU for processing.
Intermediate Surface Counter
The number of implicit surfaces generated as a result of cached surfaces.
Screen Fill Rate Counter
The number of pixels being painted per frame in terms of screens. A value of 1 represents the number of pixels in the current screen resolution – for example, 480 x 800 pixels.
You can enable or disable the display of the frame rate counters in your code. When you create a Windows Phone app project in Visual Studio, the following code to enable the frame rate counters is added by default in the file App.xaml.cs.
' Show graphics profiling information while debugging. If System.Diagnostics.Debugger.IsAttached Then ' Display the current frame rate counters. Application.Current.Host.Settings.EnableFrameRateCounter = True ' other code... End If
To disable the frame rate counters
Comment out the line of code that enables the frame rate counters as shown in the following code.
' Display the current frame rate counters. 'Application.Current.Host.Settings.EnableFrameRateCounter = True
Set EnableFrameRateCounter to false as shown in the following code.