FLOPS Calculator
Calculate the theoretical peak FLOPS (GFLOPS, TFLOPS) of a CPU or GPU from cores, clock speed and FLOPs per cycle, the sustained rate at a given efficiency, and how long a workload takes.
How it works
peak FLOPS = devices × cores × clock (Hz) × FLOPs per cycle per core · sustained = peak × efficiency · time = workload ÷ sustained FLOPS
FLOPS (floating-point operations per second) is the standard measure of compute throughput. The theoretical peak multiplies the number of cores by the clock rate and by how many floating-point operations each core can retire per cycle: a fused multiply-add counts as two, and a 256-bit AVX2 unit handles four FP64 or eight FP32 lanes. Real applications reach only part of the peak — dense matrix multiply (LINPACK) often 60–90%, memory-bound code far less — which is what the efficiency input is for.
Worked example
One 8-core CPU at 3.5 GHz with AVX2 and two FMA units (16 FP64 FLOPs per cycle) peaks at 8 × 3.5 × 10^9 × 16 = 448 GFLOPS (56 GFLOPS per core). At 70% efficiency it sustains 313.6 GFLOPS, so a 1,000 TFLOP (10^15 FLOP) job takes about 53.1 min.
Sources: Wikipedia — FLOPS (floating-point operations per cycle per core) · NVIDIA — Ada GPU architecture whitepaper (RTX 4090 peak FP32)
Frequently asked questions
How do you calculate FLOPS?
Multiply cores × clock speed in Hz × floating-point operations per cycle per core, then by the number of chips. An RTX 4090 has 16,384 CUDA cores × 2.52 GHz × 2 = 82.6 TFLOPS FP32.
What are FLOPs per cycle?
How many floating-point results one core can produce each clock. A fused multiply-add counts as 2; SIMD units multiply that by the vector width. Typical FP64 values: 4 (SSE), 16 (AVX2 with two FMA units), 32 (AVX-512 with two FMA units).
What is the difference between FLOPS and FLOP?
FLOP (or FLOPs) is an amount of work, a count of operations; FLOPS is a rate, operations per second. Training an AI model is measured in total FLOP, hardware in FLOPS.
Why is my real performance lower than the peak?
Peak assumes every core issues full-width FMAs every cycle at the boost clock. Memory bandwidth, cache misses, branches, lower all-core clocks and thermal limits usually cut that to 10–80% depending on the code.
Related calculators
This calculator is for educational purposes. Double-check important results before acting on them.