Groq LPU: no published inference throughput figure (honest negative)
Fields
benchmarks/alt-groq-no-throughput-figureNotes
HONEST NEGATIVE: Groq's own architecture page publishes no per-chip compute or memory-capacity figure at all. The 230 MB SRAM capacity, 188 TFLOPS FP16 and 750 TOPS INT8 come from press coverage of the original GroqChip (Hot Chips 2021) and are NOT confirmed on groq.com. Groq confirms only: on-chip SRAM, no off-chip HBM, 14 nm, and 80 TB/s SRAM bandwidth. No inference throughput figure is published anywhere by Groq.
LOAD-CONDITION AUDIT (bq- 2026-10-04). SCENARIO: NOT STATED by the source - absent, not inferred. A throughput figure with no scenario cannot be placed against an MLPerf Offline or Server number (they are different measurements; on identical hardware the Offline-minus-Server difference is negative in 5 of 9 systems measured). ABSENT CONDITIONS (5 of 7 checked: model, hardware, batch-or-concurrency, input length, output length, engine version, warmup): - engine version: unrecoverable from alt-groq-lpu-arch - engine_id=alt-groq-lpu-arch is named but no build/commit/container digest is published - batch/concurrency: unrecoverable from alt-groq-lpu-arch - would need the achieved in-flight batch or the --max-concurrency value - input length: unrecoverable from alt-groq-lpu-arch - would need the run's ISL or the prepared dataset's input-length profile - output length: unrecoverable from alt-groq-lpu-arch - would need the run's OSL or the harness's configured max_tokens - warmup: unrecoverable from alt-groq-lpu-arch - would need the raw harness log's warmup phase or the benchmark command line (loadgen min_duration/min_query_count, or trtllm-bench --warm_up N / --num_runs N) None of these were filled in. A plausible value is worse than an absent one: it would be trusted.