WZ-SPICE ENGINE SERIES · PART 03 · SPARSE SCALE

WIOWIZ Native SPICE at Scale: An 8T SRAM Compute Macro to 170,240 MOS Devices

Memory is the retained strength. Runtime is the open optimization problem.
WIOWIZ Technologies • August 2026 • 8 min read

Circuit simulators often change character as the matrix grows. We ran WZ-SPICE on a tiled SG13G2 SRAM compute-in-memory macro at increasing sizes, with ngspice and Xyce running the same size-specific netlists as references. The block is a regular array rather than a diverse analog design. The completed sweep reaches 170,240 expanded MOS devices.

What the WIOWIZ CIM hierarchy contains

The source block is a WIOWIZ 16 by 16 compute-in-memory tile in IHP SG13G2. One tile contains 256 8T SRAM cells, 16 three-device write-precharge circuits, and 16 read-precharge devices. Flattened for simulation, that is 2,128 MOS devices per tile.

WIOWIZ CIM tile and scale hierarchy
WIOWIZ CIM tile and scale hierarchy

Larger points repeat that designed tile while sharing global row and column nets. No synthetic transistor mesh is added. The completed 128 by 160 macro is an 8 by 10 tile grid: 80 tiles, 20,480 SRAM cells, and 170,240 MOS devices.

Macro arrayTile gridSRAM cellsExpanded MOS devices
16 by 161 by 12562,128
32 by 802 by 52,56021,280
64 by 964 by 66,14451,072
96 by 1286 by 812,288102,144
128 by 1608 by 1020,480170,240

Every SRAM cell is preloaded to one. The 10 ns transient then applies a 0.4 V row activation and exercises the transistor read and compute path. This sweep measures that preloaded compute operation; it does not include write-cycle timing.

Memory

The clearest result is memory. At every completed overnight size, WZ-SPICE used less peak RSS than both references. MiB values are rounded for display; the retained KiB values are exact.

DevicesWZ-SPICEngspiceXyce
21,28057,280 KiB / 55.94 MiB220,820 KiB / 215.64 MiB250,484 KiB / 244.61 MiB
51,072119,872 KiB / 117.06 MiB514,940 KiB / 502.87 MiB553,700 KiB / 540.72 MiB
102,144229,268 KiB / 223.89 MiB1,017,164 KiB / 993.32 MiB1,068,436 KiB / 1,043.39 MiB
170,240387,544 KiB / 378.46 MiB1,684,220 KiB / 1,644.75 MiB1,769,168 KiB / 1,727.70 MiB

Across the six completed overnight points, WZ-SPICE reported zero dense fallbacks. The factor fill ratio stayed between 1.141 and 1.142. Full values remain in the dataset.

Runtime

The trade-off is wall time.

DevicesWZ-SPICEngspiceXyce
21,280414.39 s19.55 s12.92 s
51,0721,298.72 s77.76 s122.10 s
102,1443,334.20 s268.02 s188.75 s
170,24012,098.00 s971.48 s602.03 s

At 170,240 devices WZ-SPICE took 12,098.00 seconds, compared with 971.48 seconds for ngspice and 602.03 seconds for Xyce. Across the completed overnight points it was 16.24 to 32.07 times slower than the fastest retained reference. The profiling evidence identifies model evaluation as a substantial cost. Parsing, residual evaluation, numeric factorization, and iteration control also contribute to the full wall time.

What was checked

The retained answer comparison is one node, rbl0, sampled at 5 ns. From 12,768 devices upward, the largest retained absolute difference is 2.23 microvolts against ngspice and 1.13 microvolts against Xyce. This is not a waveform-wide maximum. The 2,128, 4,256, and 8,512-device points retain runtime and memory but no voltage-difference number, so they are performance-only points.

A 255,360-device array was attempted. WZ-SPICE stopped at the 14,400-second limit with peak RSS 561,304 KiB, or 548.15 MiB. ngspice and Xyce were not run at that size. It is neither a completion result nor a cross-engine comparison.

The exact size-specific netlists and run records are retained with the study. The compared solver build identities are incomplete, so this study is not described as fully reproducible. The memory result is the present strength. Runtime is the open optimization problem, and both remain visible in the same table.

Scope

These are execution, memory, sparse-health, and single-sample voltage measurements on one regular tiled SRAM compute-in-memory macro. Memory and runtime are retained across the completed sweep. Voltage agreement is limited to rbl0 at 5 ns from 12,768 devices upward. This is not waveform-wide validation, silicon correlation, or tapeout qualification.

The sparse path stays memory-efficient through 170,240 devices. Runtime remains the clear work item.

Backing numbers

  • 170,240 devices: 387,544 KiB WZ-SPICE peak RSS
  • References at 170,240: 1,684,220 and 1,769,168 KiB
  • Zero dense fallbacks across six completed overnight points
  • 255,360-device attempt stopped at the 14,400-second limit
WIOWIZ Native SPICE Engine SeriesWIOWIZ Native SPICE: What Our Analog Simulator Runs Today WIOWIZ uPHY: Coupling FSimX and Native SPICE on a 2.5 Gb/s Recovered-Clock Link WIOWIZ Native SPICE at Scale: An 8T SRAM Compute Macro to 170,240 MOS Devices
#WZSPICE #SPICE #sparsematrix #SRAM #CIM #WIOWIZ

Our Approach

We're building systems that think about specifications the way engineers do.

We build our own AI-driven EDA with an intelligence layer across it, on a mission to autonomize the RTL-to-GDSII flow.

Walk-in ones, walk-in zeros