Performance dashboards - Qualcomm Dragonwing Documentation

Values measured on QLI 2.1.1, on two configurations: and . Each table says which one it shows.For more information, see Use overlay configurations to derive image recipes.

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	4.26	4.16
`Camera driver init finish`	7.73	Not measured
`Sysinit.target`	8.01	7.90

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

The time elapsed from power-on until the system’s first user-space process (PID 1, typically systemd) starts executing. This includes the time taken by Firmware, Loader and Kernel+InitramFS.

Camera driver init finish

Indicates that the camera hardware has completed initialization and is ready for use.

Sysinit.target

The time from power-on until sysinit.target is reached — the point where all essential system initialization services (file systems mounted, kernel modules loaded, basic hardware configured) have completed.

Measured on the . The is within 5%. Lower is better.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better, except for CPU total time, thread total time, and mutex total time, where lower is better.

Geekbench

Benchmark	Version	Score
Geekbench ST	6.5.0	1152
Geekbench MT	6.5.0	2997

CoreMark

Benchmark	Iterations/s
CoreMark	26219.192

Tiotest

Test	Configuration	Score
Sequential read · MB/s	256 MB/thread · 512 KiB blocks	497.9
Sequential write · MB/s	256 MB/thread · 512 KiB blocks	949.0
Random read · IOPS	64 MB/thread · 4 KiB blocks	52284
Random write · IOPS	64 MB/thread · 4 KiB blocks	50752

GLmark2

Benchmark	Score
GLmark2	1124
GLmark2 1920 × 1080	1036
GLmark2 offscreen	496
GLmark2 offscreen 1920 × 1080	384

Sysbench

Benchmark	Score
CPU total time (second)	3.1892
Memory bandwidth (MB/second)	4438.11
Thread total time (second)	3.4808
Mutex total time (second)	0.0043

MethodGeekbench 6.5.0 · CoreMark · Tiotest · GLmark2 · SysbenchSee procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	6144	6144
Non-Linux	594	594
Kernel static	152	153
Applications + framework	513	563
Total free memory	4884	4834

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Camera recording and snapshot latency

Camera latency for QCS6490 camera use cases, in seconds. Lower is better.

Use case	Latency definition	Latency · s
4K first snapshot latency	First time after boot, time taken from capturing an image to creating a snapshot	0.34

MethodTrace log markers (trace_pipe)See procedure

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	5.98	Not measured
`Camera driver init finish`	9.95	Not measured
`Sysinit.target`	10.38	Not measured

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

The time elapsed from power-on until the system’s first user-space process (PID 1, typically systemd) starts executing. This includes the time taken by Firmware, Loader and Kernel+InitramFS.

Camera driver init finish

Indicates that the camera hardware has completed initialization and is ready for use.

Sysinit.target

Measured on the . The is within 5%. Lower is better.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better.

Geekbench

Measured on QCS5430 FP1.

Benchmark	Version	Score
Geekbench ST	6.1.0	930
Geekbench MT	6.1.0	2106

MethodGeekbench 6.1.0See procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	6144	6144
Non-Linux	594	594
Kernel static	152	153
Applications + framework	501	561
Total free memory	4897	4836

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Camera recording and snapshot latency

The KPIs for camera latency measurement data across various QCS5430 camera use cases will be provided in a future release.

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	3.05	3.34
`Camera driver init finish`	5.84	Not measured
`Sysinit.target`	6.51	6.81

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

The time elapsed from power-on until the system’s first user-space process (PID 1, typically systemd) starts executing. This includes the time taken by Firmware, Loader and Kernel+InitramFS.

Camera driver init finish

Indicates that the camera hardware has completed initialization and is ready for use.

Sysinit.target

Measured on the . The is within 5%. Lower is better.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better, except for CPU total time, thread total time, and mutex total time, where lower is better.

Geekbench

Benchmark	Version	Score
Geekbench ST	6.5.0	636
Geekbench MT	6.5.0	1602

CoreMark

Benchmark	Iterations/s
CoreMark	15024.038

Tiotest

Test	Configuration	Score
Sequential read · MB/s	256 MB/thread · 512 KiB blocks	203.2
Sequential write · MB/s	256 MB/thread · 512 KiB blocks	292.2
Random read · IOPS	64 MB/thread · 4 KiB blocks	23429
Random write · IOPS	64 MB/thread · 4 KiB blocks	11982

GLmark2

Benchmark	Score
GLmark2	632
GLmark2 1920 × 1080	379
GLmark2 offscreen	386
GLmark2 offscreen 1920 × 1080	268

Sysbench

Benchmark	Score
CPU total time (second)	4.7
Memory bandwidth (MB/second)	2926.98
Thread total time (second)	5.1491
Mutex total time (second)	0.0144

MethodGeekbench 6.5.0 · CoreMark · Tiotest · GLmark2 · SysbenchSee procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	4096	4096
Non-Linux	367	367
Kernel static	112	113
Applications + framework	493	535
Total free memory	3124	3081

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Camera recording and snapshot latency

Camera latency for Dragonwing IQ-615 camera use cases, in seconds. Lower is better.

Use case	Latency definition	Latency · s
720p30 encode – first camera latency	The time taken, during the first instance after boot, from GStreamer connect to the first encoded video frame.	0.442

MethodTrace log markers (trace_pipe)See procedure

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	6.55*	3.76
`Camera driver init finish`	9.63*	Not measured
`Sysinit.target`	9.70*	6.91

* The boot KPI impact is seen due to the implementation of workaround for ARM errata CVE-2025-10263. See ARM errata CVE-2025-10263 for more details.

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

The elapsed time from power-on until the system’s first user-space process (PID 1, typically systemd) begins execution. This duration includes firmware initialization, bootloader execution, and kernel plus initramfs loading.

Camera driver init finish

Indicates that the camera hardware has completed initialization and is ready for use.

Sysinit.target

The elapsed time from power-on until the system reaches sysinit.target, marking the completion of essential system initialization services, including filesystem mounting, kernel module loading, and basic hardware configuration.

Measured on the . The is within 5%. Lower is better.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better unless the row says otherwise.

Geekbench

Benchmark	Version	Score
Geekbench ST	6.5.0	1037
Geekbench MT	6.5.0	3194

CoreMark

Benchmark	Version	Iterations/s
CoreMark	Not applicable	22836.264

Tiotest

Test	Configuration	Score
Sequential read · MB/s	256 MB/thread · 512 KiB blocks	331.7
Sequential write · MB/s	256 MB/thread · 512 KiB blocks	1394.7
Random read · IOPS	64 MB/thread · 4 KiB blocks	38066
Random write · IOPS	64 MB/thread · 4 KiB blocks	48973

GLmark2

Benchmark	Score
GLmark2	612
GLmark2 1920 × 1080	448
GLmark2 offscreen	368
GLmark2 offscreen 1920 × 1080	295

Sysbench

Benchmark	Score
CPU total time (s) (Lower is better)	3.6595
Memory transfer rate (MB/s) (Higher is better)	3955.46
Thread total time (s) (Lower is better)	3.9773
Mutex total time (s) (Lower is better)	0.0048

MethodGeekbench 6.5.0 · CoreMark · Tiotest · GLmark2 · SysbenchSee procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	12288	12288
Non-Linux	835	835
Kernel static	270	270
Applications + framework	600	590
Total free memory	10583	10592

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	3.43	3.06
`Camera driver init finish`	6.19	Not measured
`Sysinit.target`	5.88	5.51

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

Camera driver init finish

Indicates that the camera hardware has completed initialization and is ready for use.

Sysinit.target

Measured on the . The is within 5%. Lower is better.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better unless the row says otherwise.

Geekbench

Benchmark	Version	Score
Geekbench ST	6.5.0	1139
Geekbench MT	6.5.0	5878

CoreMark

Benchmark	Version	Iterations/s
CoreMark	Not applicable	22832.788

Tiotest

Test	Configuration	Score
Sequential read · MB/s	256 MB/thread · 512 KiB blocks	434.5
Sequential write · MB/s	256 MB/thread · 512 KiB blocks	1401.9
Random read · IOPS	64 MB/thread · 4 KiB blocks	66829
Random write · IOPS	64 MB/thread · 4 KiB blocks	78674

GLmark2

Benchmark	Score
GLmark2	2847
GLmark2 1920 × 1080	2464
GLmark2 offscreen	2602
GLmark2 offscreen 1920 × 1080	712

Sysbench

Benchmark	Score
CPU total time (s) (Lower is better)	3.6559
Memory transfer rate (MB/s) (Higher is better)	3914.28
Thread total time (s) (Lower is better)	4.2239
Mutex total time (s) (Lower is better)	0.0037

UnixBench

Benchmark	Score
UnixBench ST	1101
UnixBench MT	7564.8

MethodGeekbench 6.5.0 · CoreMark · Tiotest · GLmark2 · Sysbench · UnixBenchSee procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	36864	36864
Non-Linux	2219	2219
Kernel static	749	750
Applications + framework	1057	974
Total free memory	32838	32922

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Boot time

Milestone	UEFI · s	U-Boot · s
`Init/systemd process`	6.07	5.61
`Sysinit.target`	15.39	14.93

MethodBoot markers from systemd journalSee procedure

What the milestones mean

Init/systemd process

Sysinit.target

Measured on the . The is within 5%. Lower is better. Camera init boot time is not available: camera is not L0 enabled on CQ2390 currently.

System benchmarks

Standard benchmarks for CPU, memory, storage, and graphics. Higher is better unless the row says otherwise.

Geekbench

Benchmark	Version	Score
Geekbench ST	6.5.0	684
Geekbench MT	6.5.0	928

CoreMark

Benchmark	Iterations/s
CoreMark	20622.809

Sysbench

Benchmark	Score
CPU total time (s) (Lower is better)	10.0006
Memory transfer rate (MB/s) (Higher is better)	3204.57
Thread total time (s) (Lower is better)	10.0006
Mutex total time (s) (Lower is better)	0.321

MethodGeekbench 6.5.0 · CoreMark · SysbenchSee procedure

Memory map

Memory used by each partition and total free memory after boot, in MB. Higher free memory is better.

Partition	Upstream config · MB	Qualcomm multimedia config · MB
Total RAM	4096	4096
Non-Linux	560	560
Kernel static	111	111
Applications + framework	491	498
Total free memory	2934	2927

Method/proc/meminfo, /proc/iomem and /proc/vmstat after bootSee procedure

Camera recording and snapshot latency

Camera latency KPIs are not available for CQ2390. Camera is not L0 enabled on CQ2390 currently.

Measurement procedures

The measurement procedures include KPIs, such as boot time, system benchmark, record latency, and snapshot latency.

Measure boot time

To measure boot time, do the following:

Flash a build.

See Flash software images to boot the device.

After the device is up, reboot it.

Connect to the device console using a serial cable.

Connect a serial cable between the device and the Linux host PC.
Connect to the UART terminal using credentials ( user: root, password: oelinux123 ). See Connect to a UART shell.
Power-off and on the device.

Boot time KPIs can be measured by capturing systemd-analyze and journalctl logs after the device boots up and stabilized.

systemd-analyze > /var/lib/systemd-analyze.txt

journalctl --output=short-monotonic -b --no-pager -l > /var/lib/journalctl.txt

grep Startup /var/lib/systemd-analyze.txt

Expected output:

Startup finished in 1.697s (firmware) + 402ms (loader) + 1.693s (kernel) + 15.887s (userspace) = 19.681s

grep "camera driver initialized rc : 0" var/lib/journalctl.txt

Expected output:

[    4.220245] iq-615-evk kernel: CAM_INFO: CAM-UTIL: cam_main_probe: 336: Spectra camera driver initialized rc : 0

grep "Reached target System Initialization." /var/lib/journalctl.txt

Expected output:

[    4.757850] iq-615-evk systemd[1]: Reached target System Initialization.

Boot time till Init/systemd process = Firmware + Loader + Kernel
    = 1.697 + 0.402 + 1.693 = 3.892s
Boot time till Camera driver init finish = Firmware + Loader + journalctl timestamp of "camera driver initialized"
    = 1.697 + 0.402 + 4.220 = 6.319s
Boot time till Sysinit.target = Firmware + Loader + journalctl timestamp of "Reached target System Initialization"
    = 1.697 + 0.402 + 4.757 = 6.856s

The Firmware and Loader times are taken from systemd-analyze output (1.697s + 0.402s). The kernel timestamps in journalctl are relative to kernel start, so Firmware + Loader time is added to get the absolute boot time from power-on.

Measure system benchmarks

These benchmarks measure the performance of subsystems such as CPU throughput, memory bandwidth, memory latency, and I/O performance.

Prerequisites

Before running any benchmark, complete the following setup:

ADB isn’t enabled by default on the device. To enable ADB before running these benchmarks, see Enable ADB.

Flash the build.

Run the following command to get root access:

adb root

Open a shell on the device:

adb shell

Navigate to the directory where the binary is pushed:

cd /usr/bin

Set execute permissions on the binary:

chmod 777 <binary>

Geekbench

Geekbench is a tool used to measure system performance against the established benchmarks.To measure system performance using Geekbench, do the following:

To download Geekbench from the Linux/ARM section from upstream, see Geekbench.

The Geekbench 6 for Linux/AArch64 is a preview build. The Geekbench versions may change and the steps mentioned in this section are for your reference. The preview builds require an active Internet connection and automatically upload benchmark results to the Geekbench browser.

To measure a CPU benchmark using Geekbench, do the following: Unzip the Geekbench file and push it to the device from the host using ADB or SCP. The following are example commands:

Using ADB:

adb push Geekbench-6.3.0-LinuxARMPreview /var/cache/

Using SCP:

scp -r Geekbench-6.3.0-LinuxARMPreview root@<device-ip>:/var/cache/
cd /var/cache
chmod 777 Geekbench-6.3.0-LinuxARMPreview/*

To run Geekbench, run the following commands on the device:

cd Geekbench-6.3.0-LinuxARMPreview
./geekbench_aarch64

Sysbench

Sysbench measures CPU, memory, thread, mutex, and file I/O performance.To run Sysbench tests, run the following commands on the device:

./sysbench --test=cpu run
./sysbench --test=memory run
./sysbench --test=threads run
./sysbench --test=mutex run
./sysbench --test=fileio --file-test-mode=seqwr run
./sysbench --test=fileio --file-test-mode=seqrd run
./sysbench --test=fileio --file-test-mode=rndrd run
./sysbench --test=fileio --file-test-mode=rndwr run

To run with taskset:

taskset <taskset> ./sysbench --test=<test_name> run

Tiotest

Tiotest measures storage I/O performance.To run Tiotest, do the following:

Run the sequential I/O test:

/data/tio/tiotest -t 8 -d /data/tio -f 256 -b 524288 -k3 -k1 --direct-io sync=1

Run the random I/O test:

/data/tio/tiotest -t 8 -d /data/tio -f 64 -b 4096 -k2 -k0 2012 -r 12500 20 --direct-io sync=1

Drop the cache between iterations:

echo 3 > /proc/sys/vm/drop_caches

CoreMark

CoreMark measures embedded processor performance.To run CoreMark, run the following command on the device:

./coremark.exe

The following is an example output:

2K performance run parameters for coremark.
CoreMark Size    : 666
Total ticks      : 15268
Total time (secs): 15.268000
Iterations/Sec   : 26198.585276
Iterations       : 400000
Compiler version : GCC11.4.0
Compiler flags   : -O2 -DPERFORMANCE_RUN=1  -lrt
seedcrc          : 0xe9f5
[0]crclist       : 0xe714
[0]crcmatrix     : 0x1fd7
[0]crcstate      : 0x8e3a
[0]crcfinal      : 0x65c5

Glmark2

Glmark2 measures GPU rendering and graphics performance.To run Glmark2, do the following:

Configure the Wayland runtime environment:

export XDG_RUNTIME_DIR=/dev/socket/weston
mkdir --parents $XDG_RUNTIME_DIR
chmod 0700 $XDG_RUNTIME_DIR
export WAYLAND_DISPLAY=wayland-1

Run the off-screen test at default resolution:

./glmark2-es2-wayland --off-screen --data-path /usr/share/glmark2

Run the off-screen test at 1920x1080 resolution:

./glmark2-es2-wayland --off-screen -s 1920x1080 --data-path /usr/share/glmark2

Run the on-screen test at default resolution:

./glmark2-es2-wayland --data-path /usr/share/glmark2

Run the on-screen test at 1920x1080 resolution:

./glmark2-es2-wayland -s 1920x1080 --data-path /usr/share/glmark2

Measure memory map

A memory map provides information on how memory is allocated for different processes. A memory map measurement allows you to monitor a mapped process and troubleshoot any memory issues.To calculate the memory map, boot the device and stabilize it. Then, run the following commands to collect logs from the device:

cat /proc/meminfo

cat /proc/iomem

cat /proc/vmstat

Non-Linux memory

Use the following formula to calculate the non-Linux memory:Non-Linux = Total RAM size − Total LinuxRun the following command to calculate the total RAM size:

cat /proc/meminfo | grep -i "MemTotal"

To calculate the total Linux memory from iomem, run the following command:

cat /proc/iomem | grep System

Kernel static

Use the following formula to calculate the kernel static:Kernel static = Total Linux − MemTotal

Application + framework memory calculation

Use the following formula to calculate the memory used by the applications and framework:Application + framework = MemTotal − Free memory

Free memory calculation

Use the following formula to calculate the free memory:Free memory = MemFree + (Cached − shmem) + buffer + ION cacheTo obtain the free memory details, run the following command:

cat /proc/meminfo

To check the vmstat logs for ION cache, run the following command:

cat /proc/vmstat

Measure camera recording and snapshot latency

This topic describes the camera recording and snapshot latency measurement procedure.To complete the prerequisites on every reboot, run the following commands on the device:

mount -t debugfs none /sys/kernel/debug

setprop persist.qmmf.kpi.debug 2

First record latency

To capture the logs, follow these steps:

Boot the device and wait for it to stabilize.

In one shell, run the following command:

cat /sys/kernel/debug/tracing/trace_pipe > trace.log

In another shell, run the use case.

Stop the trace log.

See the reference table below to measure the record latency.

First snapshot latency

Boot the device.

After the device stabilizes, in one shell, run the following command:

cat /sys/kernel/debug/tracing/trace_pipe > trace.log

In another shell, run the use case.

Stop the trace log.

See the reference table below to measure snapshot latency.

Reference table for measurement

Use cases	Log marker	Calculation
Record latency	`273.082629: tracing_mark_write: B\|Connect` `273.119992: tracing_mark_write: B\|StartCamera` `276.722946: tracing_mark_write: B\|CreateVideoTrack` `276.731158: tracing_mark_write: B\|StartVideoTrack` `277.306283: tracing_mark_write: E\|FirstVidFrame\|1`	Connect to Start Camera = StartCamera − Connect StartCamera to CreateVideoTrack = CreateVideoTrack − StartCamera CreateVideoTrack to StartVideoTrack = StartVideoTrack − CreateVideoTrack StartVideoTrack to FirstVidFrame = FirstVidFrame − StartVideoTrack Rec latency = sum of above all
Snapshot latency	`303.975067: tracing_mark_write: S\|FirstCapImg\|0` `304.544265: tracing_mark_write: S\|SnapShot-Shot\|0`	Snapshot latency = snapshot − FirstCapimg

Introduction

Architecture

Key Documents

Technologies

System

Release Notes

Boot time

System benchmarks

Geekbench

CoreMark

Tiotest

GLmark2

Sysbench

Memory map

Camera recording and snapshot latency

Boot time

System benchmarks

Geekbench

Memory map

Camera recording and snapshot latency

Boot time

System benchmarks

Geekbench

CoreMark

Tiotest

GLmark2

Sysbench

Memory map

Camera recording and snapshot latency

Boot time

System benchmarks

Geekbench

CoreMark

Tiotest

GLmark2

Sysbench

Memory map

Boot time

System benchmarks

Geekbench

CoreMark

Tiotest

GLmark2

Sysbench

UnixBench

Memory map

Boot time

System benchmarks

Geekbench

CoreMark

Sysbench

Memory map

Camera recording and snapshot latency

Measurement procedures

Prerequisites

Geekbench

Sysbench

Tiotest

CoreMark

Glmark2

Non-Linux memory

Kernel static

Application + framework memory calculation

Free memory calculation

First record latency

First snapshot latency

Reference table for measurement