Hardware, VRAM, latency & economics calculator for open LLM deployments
# Generating spec...
The executable weight term multiplies parameter billions by bits divided by eight and then one point two. Seventy billion at eight bits gives eighty-four assigned gigabytes; at four bits gives forty-two. Both bars use five pixels per assigned gigabyte. The twenty percent overhead is already included in this weight term, while the source separately adds activation and cache. These written allowances do not measure checkpoint or runtime memory. For seventy billion parameters the full fine-tuning branch adds ten assigned gigabytes per parameter billion, or seven hundred. The QLoRA branch instead assigns zero point zero eight times seventy plus one, giving six point six. Both bars use zero point seven pixels per assigned gigabyte. These are source heuristic optimizer and adapter allowances, not actual trainable parameter accounting, throughput, quality or evidence that either workload fits a real device. Default inference combines eighty-four assigned weight gigabytes, four point three seven five binary gibibytes from the cache denominator, and five point six activation units, giving the mixed-unit total ninety-three point nine seven five. Its assigned eighty gigabyte H100 fixture reserves ten percent and rounds total divided by seventy-two up to two nodes. Bars show two nodes for the default versus one for an illustrative seventy-two-unit total exactly at the safe capacity. This is an arithmetic planning fixture, not a deployment, current price or hardware benchmark.