Partager via


Compact Database Extended Performance Test (Compact 2013)

3/26/2014

The CEDB Extended Performance tests analyze the performance of the system when performing common database operations such as writing a record, a seeking database, and deleting a record. They capture information about CPU utilization and memory data, as well as the time it takes to complete each operation.

* "Perf_dbEx_Long": This is the extended version of the Perf_dbEx.dll benchmark suite. It contains a larger amount of benchmark operations and data.

Please see the documentation for details about the Perf_dbEx.dll database performance tests.

You may want to run this test to compare CEDB extended performance on storage devices from different manufacturers. You may also want to run this test to decide whether to store the database on a flash card or a hard disk.

The CEDB Extended Performance test generates raw benchmark data into a log file in the release directory. The log file name is in the following format:

"perf_dbEx_long_[Target HW]_[Platform]_[OS Version].LOG".

For more details about the content of the raw log, see PerfLog Output File Contents.

You can write your own parser to convert the raw data, or use the PerfToCsv Tool, the default parser provided by Microsoft. For more information about the default parser, see Managing Performance Results Using PerfLog.

Test Prerequisites

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

There are no other hardware requirements for the CEDB Extended Performance tests.

The following table shows the software requirements for the CEDB Extended Performance tests.

Requirement

Description

Tux.exe

Tux Test Harness, required for executing the test.

Kato.dll

Kato logging engine, required for logging test data.

Perflog.dll

Performance logging engine, required for capturing the benchmark data.

Perf_dbEx_long.dll

Test library

NoteThere must be at least 10 megabytes (MB) of free space in the root directory of the device. If there is not sufficient space in the root directory of the target device, the test cannot run properly. An alternate option is to run the test suite on a storage media such as a storage card or hard disk.

Subtests

The table below lists the subtests included in this test.

SubTest ID

Description

1001

Measures the database performance by using the default sorting mechanism.

1002

Measures the database performance by using the DWORD sorting mechanism.

1003

Measures the database performance by using the String sorting mechanism.

1004

Measures the database performance by using the Filetime sorting mechanism

1005

Measures the database performance on flushing.

Setting Up the Test

This test has no additional requirements, beyond the standard test environment setup.

Running the Test

The CEDB Extended Performance test executes the command line of tux -o -d perf_dbEx_long on default execution.

The following table shows the optional command line parameters for the CEDB Extended Performance Tests.

Command line parameter

Description

/path root_path

Specifies the database volume root path.

/dbvol db_volume_filename

Specifies the database volume name.

/db db_name

Specifies the database name.

/sleep

Allows the test suite to pause between each operation.

/interval time

Specifies the interval (in milliseconds) between each CPU/memory snapshot. The default value is 100 ms.

/calibration time

Specifies the CPU calibration duration (in milliseconds). The default value is 100 ms.

Example:

tux -o -d perf_dbEx_long -c "/path \Hard Disk /dbvol testVol /db testDB"

The above command will create the database "testDB" inside the database volume file "testVol", on the root path of "\Hard Disk".

Verifying the Test

When the test completes running, verify that "PASS" appears in the test log for all subtests.

Troubleshooting the Test

The following table shows troubleshooting tips for error messages you may encounter when running the CEDB Extended Performance tests.

Error message

Solution

Skipping trim of volume \Perf_DBEx_Vol.

This is an informational message, not an error.

DB:Out of disk space

This is an indication that the system is running out of space. You may want to run the test on a larger storage media. For more information on how to specify the database volume file path, see Command Line Parameters for the CEDB Extended Performance Tests

See Also

Other Resources

File System Tests