Apex ComputeHome

Demo & benchmarks

Real-time billion-parameter LLM inference on FPGA.

15.6 tokens per second at 4.5 W—more than 2× faster and 3× more energy-efficient than CUDA on NVIDIA Jetson Orin Nano.

15.6tokens / second
4.5 Wcompute power
3.2×energy efficiency

Apex Compute demonstrates real-time, efficient billion-parameter LLM inference on FPGA hardware, significantly outperforming NVIDIA Jetson in both speed and energy efficiency. Running the Gemma 3 1B model via llama.cpp, our architecture achieves 15.6 tokens/sec at just 4.5 W, more than 2× faster and 3× more efficient than CUDA on Jetson Orin Nano.

Despite operating on slower memory, lower frequency, older process technology, and an FPGA—not an ASIC—Apex Compute consistently accelerates core transformer operations by at least an order of magnitude compared to CUDA. With a straightforward transition to a 12nm ASIC and LPDDR5 bandwidth, we expect more than 20× system speed-up and the possibility of a sub-1-watt chip capable of running billion-parameter models.

This capability lets robotics, drones, wearables, and smart-home devices run advanced AI models offline with minimal overhead, bringing AI power anywhere in the physical world.

Explore the implementation and sample Gemma 3 1B model on GitHub, or purchase a Kintex-7 board with two Apex Compute Unified Engines.

* Gemma 3 1B was tested with llama.cpp on NVIDIA Jetson with CUDA enabled. Because llama.cpp still performs some computation on the CPU, the CPU was limited to one thread. GPU-only performance is approximately 8 tokens/second, lower than the real-time demo above.

Apex Compute Architecture vs CUDA

OperationApex μsCUDA μsSpeedup12nm ASIC projection
RMSNorm of input (1,1152)0.78521.44827.33×65×
Q K V projection (1,1024)(1,256)(1,256)112.054251.7092.25×22.5×
RMSNorm for Q and K (1,1024)(1,256)2.31346.36320.04×48×
RoPE for Q and K (4,256)(1,256)2.83719.1616.75×16×
kqT + softmax + transpose v7.89537.4084.74×11.4×
Matmul for attention 4× (1,9)×(9,256)3.42671.120.75×8.2×
MVM for attention output projection75.054152.5672.03×20×
RMSNorm output projection (1,1152)0.78521.45127.33×65×
Residual add for attention output2.31312.3885.36×12.9×
RMSNorm for pre-MLP0.83621.0625.19×60×
MVM for MLP gate + GELU505.622836.4371.65×16.5×
MVM for MLP up504.809864.5491.71×17.1×
MVM for MLP down + element-wise multiply505.148325.4760.64×6.4×
RMSNorm for post-MLP0.78520.98826.74×64×
Output residual add2.64712.2624.63×11×
Large MVM (1,1152)×(1152,262144)19041.4595003.12×31.2×
Model speed15.6 tokens/s7.8 tokens/s2.00×≥ 20×
Gemma 3 — 1BApex (4.5 W)CUDA Jetson (7 W)Apex / CUDA12nm ASIC projection
Tokens / sec15.637.592.06× faster≥ 20× faster
Joules / token0.2870.9223.20× more efficient10–20× (simulation pending)

Prototype hardware comparison

SpecificationApex Kintex UltraScale+ KU5PNVIDIA Jetson Orin Nano 8GBComparison
Memory1333 MHz, 32-bit DDR42133 MHz, 128-bit LPDDR56.4× slower than NVIDIA
Engine speed333 MHz408 MHz GPU1.23× slower than NVIDIA
PrecisionINT4 / FP4 / INT8 matrix, BF16 vectorBF16 / FP32 / INT4 / INT8
Power4.5 W7 W compute module only1.56× less power
Process16nm FinFET8nm SamsungNVIDIA uses a newer process

Potential 12nm ASIC speed-up

Our design is primarily memory-bandwidth-bound for weight matrix multiplication and compute-bound for SRAM-based operations. By transitioning to LPDDR5, we can realize a proportional performance increase directly in our architecture because there are no structural bottlenecks or external overheads in the hardware.

A standard LPDDR5 controller on a 12nm process node can achieve 6400 Mbps on a 128-bit interface, delivering approximately 104 GB/s of bandwidth—about 10× higher than our current FPGA-based system. With this improvement, the design enables roughly a 20× speed-up compared to NVIDIA Jetson platforms.

At this bandwidth, our compute engine only needs to operate at 800 MHz to fully utilize the 256-pair element-processing in the Apex Compute Unified Engine Unit. We already reach 333 MHz timing closure on a 16nm FPGA, so scaling to approximately 800 MHz on a 12nm ASIC is straightforward and expected. There is a high chance we can achieve a sub-1 W compute chip capable of running billion-parameter AI models efficiently.

More benchmark results

PyTorch is less efficient than optimized CUDA kernels for LLMs. We’ve included reference benchmarks below for comparison.

Apex Compute Architecture vs PyTorch CUDA

OperationApex μsPyTorch CUDA μsSpeedup
RMSNorm of input1.678102.30960.97×
Q K V projection112.054215.661.92×
RMSNorm for Q and K2.313189.58281.96×
RoPE for Q and K2.837114.91540.51×
kqT + softmax + transpose v7.89579.74910.10×
Matmul for attention3.42620.7366.05×
MVM for attention output projection75.054134.8531.80×
RMSNorm output projection0.785114.009145.23×
Residual add for attention output2.3139.444.08×
RMSNorm for pre-MLP0.836101.668121.61×
MVM for MLP gate + GELU505.622655.2811.30×
MVM for MLP up504.809641.6561.27×
MVM for MLP down + element-wise multiply505.148637.1111.26×
RMSNorm for post-MLP0.785117.07149.13×
Output residual add2.6479.4733.58×
Large MVM19041.467140.23.53×
Model speed15.6 tokens/s2.9 tokens/s5.2×

Run it yourself

Explore the open implementation or contact us about evaluating Apex Compute for your edge-AI workload.

Contact us