We do not recommend profiling in the simulator because the simulator can distort the performance of your app.
Visual Studio is usually installed on a desktop computer. Windows Store apps run on a wide variety of devices, form factors, and processor types. Remote profiling lets you collect performance data on any device that is connected to your Visual Studio computer over a network or that is connected directly through an Ethernet cable. When you profile remotely, Visual Studio deploys the latest build of your app.
You must have a developer license installed on the remote device; you must have the Visual Studio Remote Tools installed on the remote device; and the Remote Debugging Monitor must be running on the remote device.
To install a developer license installed on the remote device, see Getting a developer license for Windows 8 Consumer Preview.
To install the Visual Studio remote tools, see Installing the Remote Debugger
To start the remote debugging Monitor, choose Remote Debugging Monitor on the Start screen.
To profile an app on a remote device, specify the name or IP address of the device in the debugging properties of your Visual Studio project. You just specify local machine deployment target, then start profiling, collecting data for all or part of the execution run, and then stop. Visual Studio then displays the results in a document window of the IDE.
To profile your app on a remote device:
In Visual Studio, open the project that you want to profile.
On the Debug menu, choose Project Properties.
Choose Debugging in the Configuration Properties node.
From the Debugger to launch list, choose Remote Machine.
In the Machine Name row, type the name or IP address of the remote device.
If the remote device is on the same subnet as the Visual Studio computer, or if the device is directly connected to the Visual Studio computer, you can choose the down arrow in the row, choose the <Locate...> item, and then select the device on the Remote Debugger connections dialog box.
You can collect profiling data for the entire run, or you can collect data only for specific scenarios.
To profile your app from the start to the end, do this:
Start the profiler. Choose Start Performance Analysis (Keyboard: ALT + F2) to start your app and start profiling immediately. You will need to accept an elevation of the Remote Debugger Monitor privileges.
Exercise the app. Run those parts of the application that you want to profile. Repeat key scenarios to get more accurate results.
Stop profiling. In the profiling document window, choose Stop profiling (Keyboard: CTRL + ALT + F2). The profiler analyzes the data and displays the Summary view of the profiling data.
To profile a specific scenario in your app, do this:
Start the profiler. Choose Start Performance Analysis Paused (Keyboard: CTRL + ALT + F2) to start your app with profiling suspended. You will need to accept an elevation of the Remote Debugger Monitor privileges.
Resume and suspend profiling. Just before you begin the scenario that you are interested in, choose Resume profiling in the profiling document window. Exercise the scenario, and then choose Pause profiling to suspend data collection. You can suspend and resume profiling as often as you choose.
Repeat key scenarios to get more accurate results.
Stop profiling. In the profiling document window, choose Stop profiling (Keyboard: CTL + ALT + F2).