z/Architecture Timing and Performance Model
Timing policy
There is no single reliable cycles-per-instruction figure for the entire z/Architecture family. Performance depends on processor generation, instruction facilities, operand alignment, cache/storage hierarchy, translation, contention, and system configuration.
Evidence levels
documented: published for a specific processor or system.derived: computed from documented values and stated assumptions.estimated: approximate planning model.unspecified: target evidence unavailable.
Performance dimensions
Record instruction mix, facility use, branch behavior, storage translation, cache assumptions, synchronization, I/O waits, and multiprocessor contention separately where measurable. CPU instruction timing must not include unmodeled operating-system or channel-subsystem time as if it were intrinsic core latency.
Reports
Every timing report identifies the processor profile, enabled facilities, system configuration and evidence class. Do not claim exact or guaranteed execution time from the generic family model.
Expert timing, voltages, and variable clocks (shared across all CPU models)
The per-CPU timing above is the architectural/behavioral view for this part.
The adjustable, quality-first timing system is shared by every CPU model in
lib/cpu and is documented once, in the package guide:
lib/cpu/TIMING.md— Voltages, Variable Clocks, and Expert Timings:SLVoltageRail(actual voltages in mV),SLCpuTiming,SLBusTiming,SLRamTiming,SLIOTiming, the Novice/Basic/Advanced/ExpertSLTimingClasstiers, and theSLTimingProfile->SLTimingManifesta compiled.sleelaimage carries so the compiler/VM honor the declared operating point.lib/cpu/components/README.md— running a CPU at spec and overclocking it (SLClockPolicy/setSpecClock/overclock), plus the RAM / storage / optical / system-bus parts bin and the DMA / GPU / native-RAM options.
Every CPU model (this one included) inherits the clock/overclock surface from
SLCPURuntime and can be assembled with those shared expert-timing, voltage,
and component options; they are a build-layer concern, not re-declared per CPU.