Share via


Image Manipulation (Compact 2013)

3/26/2014

This test suite measure the frame-rate that is achieved while an image is moved or resized using simulated gestures.

Performance logs can be found at: \\release\XRImageManipulationPerfResults.xml

Test Prerequisites

Your device must meet the following requirements before you run this test.

The following prerequisites must be met to 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

Gse2.dll

Utility that generates simulated gesture events

Subtests

The table below lists the subtests included in this test.

SubTest ID

Description

3024332

Flick a large graphic image to scroll it

3024334

Scroll a large graphic image horizontally

3024341

Pan a large graphic image to scroll it

3024342

Zoom a large graphic image in and out

3024343

Pan a large photo image to scroll it

3024344

Flick a large photo image to scroll it

3024345

Zoom a large photo image in and out

3024346

Scroll a large photo image horizontally

3028435

Scroll a large graphic image vertically

3028436

Scroll a large photo image vertically

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

s tux -o -d \release\XRPerfImageManipulationTests.dll -c data=\release\xamlruntime\test\perf\ImageManipulation\ImageManipulation.TestSuite.xml;repeats=<repeats>;<UseBaml> -x <test#>

Argument

Description

Repeats

How many times to run the test. 3 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. Here are the recommended tests:

(1) Pan a large graphic image to scroll it

(2) Flick a large graphic image to scroll it

(3) Zoom a large graphic image in and out

(4) Scroll a large graphic image horizontally

(5) Scroll a large graphic image vertically

(11) Pan a large photo image to scroll it

(12) Flick a large photo image to scroll it

(13) Zoom a large photo image in and out

(14) Scroll a large photo image horizontally

(15) Scroll a large photo image vertically

Verifying the Test

This test reports a Pass or Fail result.

The Image Manipulation test logs can be found in the CTK log directory:

  • XRImageManipulationPerfResults.xml

The following values are common performance measurements:

  • Average Frame Rate Change Average - frame per second during Animation in frames per second (fps)
  • Load Image from Resource Average - average time for loading images from dll resource 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 fail cause lower-end devices to run out of memory, failing the test.

If running from cmd:

Re-run the test from command line with the following parameter at the end: -f Logfile.txt. The log file, which can be found the release directory after the test executes will have more detailed information on the failure.

If running from a test framework:

Open the test framework’s log file for a more detailed information on the failure.

See Also

Other Resources

Shell Tests