PDP-8 Timing and Performance
Model-specific timing
Timing differs across PDP-8 implementations and options. The architecture profile alone is insufficient to establish exact cycles or elapsed time.
Metrics
Where data is available, distinguish instruction execution, memory access, I/O wait, interrupt handling, and optional arithmetic-unit activity.
Evidence classes
documented: timing published for a named model.derived: calculated from documented values and assumptions.estimated: approximate simulator value.unspecified: no reliable model-specific value available.
Do not label this functional model cycle-accurate without comparison against hardware documentation and suitable tests.
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.