Benchmark Workload

Concept

A benchmark workload is a standardized set of programs or computational tasks used to evaluate and measure the performance, correctness, or overhead characteristics of a computing system or platform. In computer architecture and systems research, benchmark workloads exercise specific hardware or software features (such as CPU subsystems, memory protection mechanisms, or communication fabrics) and produce quantitative metrics like instruction counts, execution time, latency, and resource utilization that allow comparison across implementations.

First seen 6/21/2026

Last seen 6/21/2026

Evidence 2 chunks

Wiki v1

WIKI

Benchmark Workload

Definition

A benchmark workload is a standardized collection of programs, kernels, or computational tasks used to evaluate the performance, overhead, or functional behavior of a computing system or platform. Benchmark workloads are typically selected to exercise representative components of the system under test — such as the CPU pipeline, memory subsystem, interconnects, or protection mechanisms — so that quantitative metrics (e.g., instruction count, execution time, latency, power consumption) can be measured and compared across implementations.

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

1 connections

CHERI-RISC-V VP++ ← evaluates 100% 2e

CHERI-RISC-V VP++ was used to run 10 benchmark workloads on CheriBSD.

LINKED ENTITIES

1 links

CHERI-RISC-V VP++ EVALUATES Extracted graph relationship

CITATIONS

6 sources

6 citations — click to expand

[1] The CHERI-RISC-V VP++ virtual platform was used to run a CheriBSD boot plus 10 benchmark workloads, exercising the full CHERI trust/protection chain including ISA, MMU, memory, privilege, and capability. Bringing CHERI Capabilities to Life in a Virtual Platform: CHERI-RISC-V VP++ (ASP-DAC 2026)

[2] Measured average instruction overhead for CHERI-enabled workloads was 1.47×, with a peak overhead of 1.83×. Bringing CHERI Capabilities to Life in a Virtual Platform: CHERI-RISC-V VP++ (ASP-DAC 2026)

[3] Benchmark workloads run on CheriBSD in the case study include dhrystone, whetstone, peg, linear (100x100-sp, 10k-sp), alg-mid (125k), loops-all-mid, nnet_test, parser, radix2 (big_64k), sha_test, and zip_test, with per-workload instruction counts broken down across Integer Access, Float Access, CHERI Access, Integer Others, Float Others, and CHERI Others instruction classes. Bringing CHERI Capabilities to Life in a Virtual Platform: CHERI-RISC-V VP++ (ASP-DAC 2026)

[4] CHERI memory protection is enforced during benchmark workload execution: an in-address-space security exception on a capability store caused the OS to terminate the program while the system continued running. Bringing CHERI Capabilities to Life in a Virtual Platform: CHERI-RISC-V VP++ (ASP-DAC 2026)

[5] The MiBench automotive benchmark workloads were used on a Raspberry Pi embedded platform to evaluate the REORDER schedule-obfuscation protocol for dynamic-priority real-time systems (EDF). REORDER: Securing Dynamic-Priority Real-Time Systems Using Schedule Obfuscation

[6] The PARSEC benchmark workloads were used to evaluate the Dynamic Partition Merging multicast routing algorithm, achieving up to 23% improvement in average packet latency and 14% in power consumption against an existing multipath routing algorithm. Efficient On-Chip Multicast Routing based on Dynamic Partition Merging