tiny.profiling

Overview · API · Code relationships · Verification · Audit

Overview

Controlled performance experiments across repository workloads.

Isolated timings vary with code layout, host thermal state, and execution order. Meaningful comparisons across packages require common workload definitions, explicit host and build identity, and repeated trials evaluated as empirical distributions. Controlled perturbation experiments estimate localized performance effects under these specific conditions, but they do not produce universally reproducible evidence or reveal unconstrained speedup potential.

Definitions

Actions

Public operations.

• main

Namespaces

Public namespaces.

• json
• host
• substitute
• analyze
• driver
• fingerprint
• recovery
• surface
• capture
• code_layout
• experiment
• help
• ingest
• ir
• iteration
• report
• reduction
• catalog
• scenario
• schema
• allocation
• environment
• metric
• memory
• execute
• plan
• question
• priority
• perturbation
• order
• budget
• measurement
• record
• baseline
• cycle
• command
• options

Code relationships

Direct static dependencies extracted from parsed source by semantic graph analysis.

Uses: tiny.alloc, tiny.bench, tiny.choir, tiny.coz, tiny.http, tiny.machine, tiny.memtrace, tiny.pdf, tiny.sdfii, tiny.smg, tiny.sys, tiny.tracy, tiny.zen
Used by: tiny.bench, tiny.deadalloc, tiny.gpu, tiny.preserves, tiny.smg

Verification

No verification records are cataloged for this module in this build.

Audit