On March 22nd, someone in the LocalLLaMA community quietly posted a Docker and vLLM configuration for running Qwen3-5-122B-A10B-NVFP4 — a 122-billion-parameter mixture-of-experts model quantized to NVIDIA's FP4 format. No fanfare. No benchmark claims. Just the kind of careful, practical contribution that emerges when an engineer has spent real hours forcing a large model into a shape that actually runs. The model name alone tells a compressed story: Qwen3.5, 122B total parameters, roughly 10 billion active at any time through the MoE routing, squeezed further into FP4 precision to fit within the memory envelope of accessible NVIDIA hardware. The post has sat largely unnoticed since, which says less about its value and more about how much noise surrounds anything with a large parameter count right now.
If confirmed and reproducible, what this represents is a working deployment path for a genuinely capable model on hardware that most small teams and serious individuals can actually access. The combination of MoE architecture and FP4 quantization is specifically designed to make the parameter count misleading in the best possible way — you get the reasoning depth of a 122B model while only activating a fraction of it per token, and you store the weights at a precision that cuts memory requirements dramatically. A working Docker and vLLM config is the difference between a model existing on paper and a model running in production. The second-order effect is that community-maintained deployment configs like this one often become the quiet foundation for a dozen downstream projects — fine-tuners, API wrappers, internal tools — none of which would have started without someone doing this groundwork first.
Watch for the post gaining traction as the Qwen3.5 model family attracts broader attention, or for other community members posting reproducibility results and hardware specs. Either would meaningfully change the picture.
<!-- SC_OFF --><div class="md"><p>I could not find good data points on what speed one could get with a single 5090 and enough DDR4 RAM. </p> <p>My system: AMD EPYC 7532 32core
<!-- SC_OFF --><div class="md"><p>I'm currently choosing between IQ3_XXS Qwen-3.8-Flash and Q8_0 27B.</p> <p>This month I don't have anything complex enough to justify either's
<!-- SC_OFF --><div class="md"><p>Hi,</p> <p>I taught Computer Science for 30 years in a French School of Electrical Engineering, Computer Science Department.</p> <p>I recently
  submitted by   <a href="https://www.reddit.com/user/tedivm"> /u/tedivm </a> <br /> <span><a href="https://github.com/tedivm/qwen36-27b-docker">[link]</a></span>  
<!-- SC_OFF --><div class="md"><p>Long post, but hopefully helps somebody. Llama-cpp vulkan server running single AMD R9700. The settings below are showing great results with a
<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1sa060l/5950x_asrock_570m_pro_4_fully_headless_vllm_box/"> <img alt="5950x + ASrock 570m PRO 4 = fully
<table> <tr><td> <a href="https://www.reddit.com/r/singularity/comments/1s7rcwr/qwen35_omni_qwens_latest_generation_of_fully/"> <img alt="Qwen3.5 Omni - Qwen’s latest generation
<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1t45m77/qwen_36_27b_looping_problem/"> <img alt="qwen 3.6 27B looping problem"
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →