Briefing

Running Minimax 2.7 at 100k Context on Strix Halo

ai-dev
by /u/Zc5Gwu · Llama

Configure llama-server with flags to run Minimax 2.7 at 100k context on Strix Halo, using no-mmap, no-context-shift, kv-unified, etc.

What to do now

Configure llama-server with the provided flags and adjust GPU swap and OOMScoreAdjust as recommended.

Summary

The Reddit post details how to run the Minimax 2.7 model on a Strix Halo GPU with a 100,000 token context window. The author uses llama-server with the unsloth/MiniMax-M2.7-GGUF:UD-IQ3_XXS checkpoint and a long list of command‑line flags. Key flags include --no-context-shift to detect context exhaustion, --no-mmap to avoid memory mapping, and -np 2 with --kv-unified to share a single cache across two concurrent sessions. The configuration also sets --cache-ram 0 so the cache stays in VRAM, and uses -b 1024 -ub 1024 to speed up prefill. The author recommends increasing swap size and setting OOMScoreAdjust=500 in systemd to prevent the kernel OOM killer from terminating the process. The post explains that the model performs well at coding tasks but is less balanced than Qwen3.6 27b for non‑coding scenarios. Performance screenshots show the model handling 100k context without corruption. This configuration demonstrates that with careful flag tuning, Minimax can run at high context on modest hardware, offering a practical approach for developers needing large‑context inference.

Key changes

  • Use --no-context-shift to detect context exhaustion
  • Enable --no-mmap to avoid memory mapping and OOMs
  • Set -np 2 with --kv-unified to share a single cache across two concurrent sessions
  • Set --cache-ram 0 so the cache stays in VRAM
  • Use -b 1024 -ub 1024 to improve prefill performance
  • Set --cache-reuse 256 to attempt smart cache reuse
  • Set -c 100000 to configure a 100k token context window

Affects

internal

Customer impact

Analyzing matches…

Ask about this story

Impact on an agency? Which customers? Compare historically Risks of waiting