Screen Transition (Compact 7)
3/12/2014
This test suite measures the frame-rate that is achieved when an application animates from one screen to another.
Performance logs can be found at: \\release\XRScreenTransitionPerfResults.xml
Test Prerequisites
Your device must meet the following requirements before you run this test.
The Silverlight for Windows Embedded Performance Test suite can be run on any connected device. Some of the tests may run out of memory on devices with less than 256 MB of memory.
The following table shows the software requirements for the Windows Embedded Compact-based device that will be running the performance test suite. In addition, the run-time image for the devices must include support for Silverlight for Windows Embedded (SYSGEN_XAML_RUNTIME) and CEPerf (IMGCEPERF).
| Requirement | Description |
|---|---|
Tux.exe |
Tux test harness, required for executing the test. |
Kato.dll |
Kato logging engine, required for logging test data |
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
3024353 |
Wizard screens sliding in and out-preloaded in the visual tree |
3024354 |
Wizard screens zooming in and out-preloaded in the visual tree |
3024356 |
Complex screens sliding in and out-preloaded in the visual tree |
3024357 |
Complex screens zooming in and out-preloaded in the visual tree |
3024355 |
Wizard screens loaded on demand |
3024358 |
Complex screens loaded on demand |
Setting Up the Test
For each of the tests it is recommended that you first clear the log file (unless you wish to aggregate the results of a number of tests into a single log file). Enter the following at the command line in order to clear the log file:
log 0x0
y
log -flush
Running the Test
Enter the following at the command line:
s tux -o -d \release\XRPerfScreenTransitionTests.dll -c data=\release\xamlruntime\test\perf\ScreenTransition\ScreenTransition.TestSuite.xml;repeats=<repeats>;<UseBaml> -x <test#>
| Argument | Description |
|---|---|
Seconds |
How many seconds to run the test. 30 is typically a good value. |
UseBAML |
If this is included, the test will run using a binary form of XAML which loads faster. |
Test# |
Which of the tests to run. The recommended tests are as follows: |
(1) Wizard screens sliding in and out-preloaded in the visual tree
(2) Wizard screens zooming in and out-preloaded in the visual tree
(3) Wizard screens loaded on demand
(4) Complex screens sliding in and out-preloaded in the visual tree
(5) Complex screens zooming in and out-preloaded in the visual tree
(6) Complex screens loaded on demand
Verifying the Test
This test reports a Pass or Fail result.
The logs can be found in the CTK log directory:
| • | Applications Load tests: XRAppLoadPerfScenario.xml |
|---|---|
• |
Background Animation: XRBackgroundAnimationPerfResults.xml |
• |
Image Manipulation: XRImageManipulationPerfResults.xml |
• |
List Performance Tests: XRListPerfResults.xml |
• |
Screen Transitions: XRScreenTransitionPerfResults.xml |
The following values are common performance measurements:
| • | Avg Frame Rate\ChangeAverage - frame per second during Animation, in fps (frames per second) |
|---|---|
• |
Load Image from Resource\Average - average time for loading images from dll resource in microseconds |
• |
Load Image from File\Average - average time for loading images from files, in microseconds |
• |
Create Host From Xaml\Average - average time for loading and parsing xaml and generating the visual element tree, in microseconds |
• |
Paint Element Tree\Average - average time for rendering the visual element tree , in microseconds |
• |
First Paint - time from process launch to the end of the first rendering of the visual element tree, in microseconds |
Troubleshooting the Test
Known issues: Tests with large resources may cause lower-end devices to run out of memory, failing the test.
If you are running the test from a command prompt:
Re-run the test from the command prompt with the -f Logfile.txt parameter at the end. The log file, which can be found in the release directory after the test executes, contains more detailed information on the failure.
If you are running the test from a test framework:
Open the test framework’s log file for a more detailed information on the failure.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.