benchmark

Name: benchmark
Availability: InStock
Author: solitasroh

Measure MCU, MPU, and WPF build resource usage with delta analysis.

2|1|Updated Mar 22, 2026

Search Tags:#performance #analysis #build #embedded #benchmark #trends #size

Ready to run

npx skills add https://github.com/solitasroh/rkit --skill benchmark-solitasroh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/solitasroh/rkit/tree/main/skills/benchmark
Command: npx skills add https://github.com/solitasroh/rkit --skill benchmark-solitasroh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmarking MCU/MPU/WPF builds and resource usage across platforms to identify performance and capacity bottlenecks, enabling data-driven optimization.

Core Features & Use Cases

MCU: measure flash and RAM usage via size tooling.
MPU: measure rootfs/image size for deployment planning.
WPF: measure build time and publish size for release governance.
Use Case: Compare current builds to historical benchmarks to detect regressions and forecast resource pressure.

Quick Start

Run the benchmark workflow to collect current metrics and compare them against historical trends.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I measure MCU flash and RAM usage to detect resource pressure?▼

MCU resource measurement uses arm-none-eabi-size tooling to analyze flash and RAM consumption. This benchmark automates size collection across platforms, applying delta analysis to identify current capacity bottlenecks and forecast future memory pressure.

What is the best way to track build size regressions across historical releases?▼

Build size regression tracking requires a persistent history file at .rkit/state/benchmark-history.json. This benchmark automates historical trend reporting by comparing current build metrics against past entries to detect resource usage regressions over time.

Can I benchmark WPF build time and publish size for release governance?▼

WPF build time and publish size benchmarking is fully supported for release governance. The workflow measures compilation duration and output size, then compares the results against historical trends to ensure release artifacts remain within acceptable limits.

Do I need standard toolchains and log archives to measure MPU rootfs image size?▼

MPU rootfs image size measurement requires standard toolchains and log archives. The benchmark automates deployment planning by measuring rootfs and image size across platforms, applying delta analysis to identify capacity constraints.

Does benchmarking resource usage across MCU, MPU, and WPF platforms require separate workflows?▼

Benchmarking resource usage across MCU, MPU, and WPF platforms does not require separate workflows. A single benchmark workflow automates measurement across all three environments, collecting flash, RAM, rootfs, and publish size metrics for unified trend reporting.