Windows Phone Application Performance Analysis

When you create an application with a killer user interface, you ought to consider various performance parameters of your application as well. There are certain eligibility performances criteria your application must pass to be accepted in the Marketplace. These criteria may check your application for

  • Maximum memory usage
  • Launching time of your application
  • How responsive is your application

There is the Market Place Test Kit you can use to test the likelihood of your application accepted by the marketplace.

Measuring performance of your application should always be an essential task of your application creation life cycle.

Performance analysis in windows phone

In Windows Phone 7.1 you get a Performance Analysis Tool. This tool helps you to do analysis on

  • CPU usage
  • Memory Usage
  • How you are handling garbage collection
  • What is your application frame rate

You get the performance analysis tool by either by pressing ALT+F1 or selecting it from Debug menu option.

start Performance analysis in windows phone

There are few thumb rules you need to follow to get the best results out of the performance analysis tool

  • You should target the device rather emulator
  • Run the project in release mode rather than debug mode

Just after clicking on Start Widows Phone Performance Analysis, you will get an empty performance log created for you in the solution explorer.

Performance log in windows phone

When you choose for performance analysis, you will be prompted to choose from two options

  • Execution
  • Memory 
Context switching in windows phone

Choose your option and click on Launch Application. The application will be launched with performance analysis.

Come back to Visual Studio and click on Stop Profiling. You will get progress messages that analyzed data is being created.

Context switching

windows phone Context switching

When you click on the .sap file you will get a performance graph as below,

sap file in windows phone

Frame Rates provides information about the number of frame redrawn each second. This information is only available when the display UI is getting updated. Windows Phone 7 application should have 30 to 60 second frame rate per second.

In CPU usage there are four colors and each color have its own significant meaning.

CPU usage in windows phone

Memory usage says the amonut of phone memory used in your application. It is measured in Megabytes 

The storyboard gives information about animation in the application. There are two types of animation which are represented by two different colors.

story board in windows phone

Image loads says about image load as assets into the phone memory.

GC events say about when garbage collector collects free memory.

By having all the information discussed above you can very much do performance analysis of your application. Have a good time writing good performance centric application

If you find my blogs useful you may like to follow me on twitter or may like Facebook page of my blog If you want to see post on a particular topic
please do write on FB page or tweet me about that, I would love to help you.

[twitter-follow screen_name='debug_mode' show_count='yes']

Similar Articles