Can I run Qwen3.8-27B-TWIN-TURBO-Fable-Cold-Fusion-709-ULTRA-HERETIC-Uncensored-NM-DAU-NEO-MTP-GGUF on an NVIDIA H100?

Yes

Its Q8_0 file (30.2 GB) fits in the 72.0 GB an NVIDIA H100 can use, with room for ≈ 256K tokens of context.

Full analysis of Qwen3.8-27B-TWIN-TURBO-Fable-Cold-Fusion-709-ULTRA-HERETIC-Uncensored-NM-DAU-NEO-MTP-GGUF Everything that runs on NVIDIA H100 Get the Q8_0 file on Hugging Face

ollama run hf.co/DavidAU/Qwen3.8-27B-TWIN-TURBO-Fable-Cold-Fusion-709-ULTRA-HERETIC-Uncensored-NM-DAU-NEO-MTP-GGUF:Q8_0

Files and context on NVIDIA H100

Each file of Qwen3.8-27B-TWIN-TURBO-Fable-Cold-Fusion-709-ULTRA-HERETIC-Uncensored-NM-DAU-NEO-MTP-GGUF (and of GGUF versions the site has analyzed), and how much context fits next to it, with the context cache in 16-bit or 8-bit.

File	Size	On NVIDIA H100	Context (16-bit)	Context (8-bit)
Q8_0	30.2 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-Q8_0	29.8 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-MTP-Q6_K	24.0 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-Q6_K	23.6 GB	Fits	256K	256K
Q6_K	22.4 GB	Fits	256K	256K
Q5_K_M	21.2 GB	Fits	256K	256K
Q5_K_S	20.6 GB	Fits	256K	256K
Q4_K_M	18.5 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-Q4_K_M	18.0 GB	Fits	256K	256K
IQ4_NL	17.8 GB	Fits	256K	256K
Q4_K_S	17.5 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-MTP-IQ4_XS	17.0 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-IQ4_XS	16.6 GB	Fits	256K	256K
IQ4_XS	15.3 GB	Fits	256K	256K
Qwen3.8-27B-TTURBO-Fable-C-Fusion-709-U-Httic-Uncen-NM-DAU-NEO-MAX-MTP-IQ3_M	14.5 GB	Fits	256K	256K
IQ3_M	14.1 GB	Fits	256K	256K
IQ2_M	12.1 GB	Fits	256K	256K

Qwen3.8-27B-TWIN-TURBO-Fable-Cold-Fusion-709-ULTRA-HERETIC-Uncensored-NM-DAU-NEO-MTP-GGUF on other hardware

Popular models that run on NVIDIA H100

Assumes 90% of the card's memory is usable and at least 4K tokens of context for one conversation, with the context cache in 16-bit unless noted. Fits leaves at least 20% of that memory for context; Tight leaves less.