Read the explanation
The executable INT4 lookup uses point five five bytes per parameter, despite initial text showing point five. For seven billion parameters, division by two to the twentieth, a five percent allowance, and rounding give three thousand eight hundred fifty-five binary mebibytes. FP16 at two bytes gives fourteen thousand nineteen. Both bars use point zero three pixels per mebibyte. These are assigned tensor estimates, not verified checkpoint sizes or real device allocations. The cache multiplies two for keys and values, thirty-two layers, full hidden dimension four thousand ninety-six, two thousand forty-eight tokens, batch one, and two bytes per value. Dividing by two to the twentieth yields one thousand twenty-four binary mebibytes. Doubling context gives two thousand forty-eight. Both bars use point two pixels per mebibyte. This uses the full hidden dimension without a separate grouped-head reduction, so it is the saved architecture assumption, not a measured cache shape. The default sums fifteen hundred OS reserve, one thousand twenty-four CUDA context, three thousand eight hundred fifty-five weights, one thousand twenty-four cache and five hundred seventy-eight workspace. Total is seven thousand nine hundred eighty-one against eight thousand one hundred ninety-two, leaving two hundred eleven. Both bars use point zero five pixels per assigned binary memory unit. Positive headroom below twelve percent triggers WARN rather than SAFE. Preset specifications and the bandwidth-derived token estimate are assumptions, not current hardware or performance verification.