This note complements bk_profiler and focuses on the shared level names used by BenchKit.
single- one measurement run
simple- five measurement runs
standard- eleven measurement runs
detailed- seventeen measurement runs
These names are BenchKit-level presets. Each profiler adapter defines the concrete behavior behind them.
single- event set
pa1
- event set
simple- event set
pa1..pa5
- event set
standard- event set
pa1..pa11
- event set
detailed- event set
pa1..pa17
- event set
Default report behavior for fapp is:
singletext
simpleboth
standardboth
detailedboth
Here both means text summaries plus CSV reports.
BenchKit stores profiler metadata in meta.json inside padata.tgz, and also copies a compact summary into result.json as profile_data.
This makes it possible to inspect profiler coverage without downloading the archive first.
- Results list
Profilershowstool / level- the secondary line shows
report_formatand run count
- Result detail
PA Data Summaryshows tool-specific events, explicit events, and report kinds
The summary is compact enough for portal browsing, while meta.json remains rich enough for future estimation packages to judge applicability from:
toollevelreport_kinds