Qwen3.8-Flash-Next 4.05bpw EXL3 solo launch (TabbyAPI + ExLlamaV3, 5090+4090) A developer published a serving configuration for the turboderp/Qwen3.8-Flash-Next-exl3-4.05bpw EXL3 quant, running the large MoE model split across an RTX 5090 and RTX 4090 with 192 GB of DDR5 system RAM via ExLlamaV3 v1.4.8 and TabbyAPI. The setup offloads 20 MoE layers to CPU and validates at 262K context with roughly 2,750 T/s prefill and 59 T/s decode, with an FP16-KV sibling config reaching about 2,370 T/s prefill and 55 T/s decode. Serving config for the turboderp/Qwen3.8-Flash-Next-exl3-4.05bpw EXL3 quant as a single big-MoE model split across two GPUs + system RAM. HW: RTX 5090 GPU0 + RTX 4090 GPU1 + 192 GB DDR5, Ryzen 9 7950X3D 16c/32t . CUDA 13.3. Engine pins: ExLlamaV3 v1.4.8 d21d38c , dev branch , TabbyAPI 0.0.1 @ b75fe27 , run via python main.py from the tabbyAPI checkout. export CUDA DEVICE ORDER=PCI BUS ID export CUDA VISIBLE DEVICES=0,1 0=5090, 1=4090 CPU MoE offload + D2H/compute handoff tuning export EXL3 MOE ARENA HUGEPAGE=1 hugepage-backed CPU expert arena export EXL3 MOE CPU THREADS=24 24 sweet spot on 16c/32t 32 oversubscribes export EXL3 MOE CPU PIN=1 pin to distinct physical cores export EXL3 MOE CPU SWIZZLE=1 AVX512-VBMI band-contiguous expert layout export EXL3 MOE CPU STAGE THREADS=8 staging memcpy threads default 4 export EXL3 MOE CPU SLOT ROWS=128 CPU-tail rows/slot default 64 export EXL3 MOE CPU SLOTS=8 job-ring depth default 4 export EXL3 MOE STREAM BATCH EXPERTS=32 experts per weight-staging DMA default 24 export EXL3 NGRAM STREAM=0 39 GB n-gram table stays in RAM Validated @262K: ~2,750 T/s prefill, ~59 T/s decode. cd tabbyapi-cwd/ CWD must hold the model-specific config.yml python