What GPU do I need to run upstage/Solar-Open-100B?

102.7B parameters, published in BF16. View on Hugging Face

102.7B
Parameters
BF16
Native precision
SolarOpenForCausalLM
Architecture
text-generation
Pipeline

Solar-Open-100B is published by upstage on Hugging Face, with 14,753 downloads and 495 likes to date. It's a SolarOpenForCausalLM model built for text-generation, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF16191.2 GB229.4 GBRTX A60005$1.82/hr
FP8 (quantized)95.6 GB114.7 GBAMD MI300X1$2.63/hr
cheaper alt.RTX 4000 Ada6$1.32/hr
INT4 (quantized)47.8 GB57.4 GBA1001$1.31/hr
cheaper alt.RTX A50003$0.528/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Solar-Open-100B at its published (BF16) precision: 5× RTX A6000, at $0.363/hr per GPU ($1.82/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Solar-Open-100B: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 196,608 bytes at 16-bit.

ContextKV cache, one sequence
4K0.75 GB
32K6.0 GB
128K24.0 GB

Computed from the layer, head and window counts in the model's own configuration (upstage/Solar-Open-100B), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Solar-Open-100B: common questions

Can Solar-Open-100B run on a single GPU?

No. At BF16 it needs 229.4 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest capable card in the live feed is a 48.0 GB RTX A6000, and it takes 5 of them.

How many GPUs do I need to run Solar-Open-100B?

5 at BF16. It needs 229.4 GB of VRAM and the cheapest capable live offer is a 48.0 GB RTX A6000, so 5 of them come to $1.82/hr in total.

Does quantizing Solar-Open-100B lower the GPU bill?

Yes. At BF16 the cheapest live fit is 5 RTX A6000 cards at $1.82/hr. At INT4 (quantized) it drops to one A100 at $1.31/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More SOLAR models

All 6 SOLAR models: VRAM and GPU requirements

Alternatives at this size

Other models for text-generation within about a third of Solar-Open-100B's 102.7B parameters, from other model lines.

More on Solar-Open-100B

Related reading: RTX A6000 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.