Running MiniMax M2.7 Q8_0 128K on 2x3090 with CPU Offloading – Real-World Benchmarks and Config

In a recent r/LocalLLaMA post, a user shares their experience pushing the MiniMax M2.7 model (at Q8_0 quantization) to 128K context on a 2x3090 setup with 256GB DDR4 and a secondhand 10900X CPU. The key challenge: running a large MoE model with unquantized KV cache on relatively low-end hardware for its class.
Performance Numbers
The user reports:
- Prompt processing: ~50 tokens per second
- Token generation: ~10 tokens per second
- Described as “very slow but usable for coding agent workflows”
Configuration
They use ik-llama-cuda (a llama.cpp fork) with the following flags (from their NixOS config):
${ik-llama-cuda}/bin/llama-server \
-m ${modelPath} \
--host 0.0.0.0 \
--port ${toString cfg.port} \
-c ${toString cfg.contextLength} \
-ngl 999 \
--cpu-moe \
-sm graph \
-fa on \
-t 16 \
-tb 16 \
-b 4096 \
-ub 4096 \
-np 1 \
-muge \
-ger \
--jinja \
--metrics \
--temp 1.0 \
--top-p 0.95 \
--top-k 40 \
--min-p 0.01Notable flags:
--cpu-moe– offloads MoE expert computation to CPU-sm graph– enables graph-based scheduling-fa on– flash attention-t 16/-tb 16– 16 threads for compute and batch respectively-b 4096/-ub 4096– batch and ubatch size-muge– memory-usage-guided expert loading (probably)-ger– GPU expert routing
Context & Motivation
The user reports Q8_0 was chosen to mitigate “weird behavior” seen at lower quants. They note that the model’s draft model for speculative decoding was not released for M2.7, which could have improved speed. They are primarily interested in accuracy over speed, as long as generation doesn’t take “literally all day.”
Takeaway for Developers
This is a practical datapoint for anyone running large MoE models on multi-GPU setups with system RAM. The --cpu-moe approach allows scaling context far beyond VRAM limits, albeit at reduced speed. For coding agent workflows where latency is less critical, this tradeoff may be acceptable.
📖 Read the full source: r/LocalLLaMA
👀 See Also

A Two-Step AI Workflow for Legacy Code Modernization
A Reddit post outlines a two-step 'reverse engineering' approach for using AI with legacy code: first extract business logic into a technology-agnostic Business Requirement Document, then use a 'Master Architect' prompt to rebuild from scratch with modern best practices.

Cut OpenClaw Boot Tokens 43% by Slimming Tool & Memory Files
Reduced boot tokens from ~9,457 to ~5,400 (43% drop) by converting TOOLS.md to an index, moving tool details to separate files, and implementing staged memory promotion.
Run a Second OpenCLAW Instance as a Safety Net
Deploy a basic OpenCLAW instance with key models to troubleshoot your main instance when it crashes. Works on Raspberry Pi, phone, or Clawx.

Using Project Narratives to Maintain OpenClaw Context on Long-Term Projects
A developer shares a technique for creating 'project narratives' where a separate OpenClaw worker analyzes the codebase after milestones to document system understanding, identify issues, and maintain context.