A developer released a repo helping DGX Spark users with a spare 10-24 GB GPU move the spec-decode draft model off the Spark onto that GPU. The freed memory can be used for larger context or better quantization quality. It works on a single Spark or a Spark cluster and ships as eugr-vllm-compatible mods.
Users testing DeepSeek-V4-Flash-0731 with llama-server report that the DSpark draft model delivers only 1-2 tokens per second, far slower than the MTP draft model's 30-40 t/s. They seek advice on configuring speculative decoding correctly, while another user asks how to free OS RAM when serving the model on 2x DGX Spark systems.
Users testing DeepSeek-V4-Flash-0731 with llama-server report that the DSpark draft model delivers only 1-2 tokens per second, far slower than the MTP draft model's 30-40 t/s. They seek advice on configuring speculative decoding correctly, while another user asks how to free OS RAM when serving the model on 2x DGX Spark systems.
A developer released a fork of Raymond's llama.cpp KV cache streaming project that adds hot-swappable speculative decoding, letting the draft model (MTP or DFlash2) be ejected from VRAM and reloaded as context grows. It runs Qwen 3.8 27B UD-IQ4_XS on a 16GB RTX 5060 Ti, raising token generation speed versus standard llama.cpp host-RAM offloading.
A developer released a fork of Raymond's llama.cpp KV cache streaming project that adds hot-swappable speculative decoding, letting the draft model (MTP or DFlash2) be ejected from VRAM and reloaded as context grows. It runs Qwen 3.8 27B UD-IQ4_XS on a 16GB RTX 5060 Ti, raising token generation speed versus standard llama.cpp host-RAM offloading.
A user shares a reference setup for running DeepSeek-V4-Flash-0731 on a single NVIDIA GH200 using DSpark and UVA offload, since the 284B MoE model does not fit in 144GB HBM. The post credits prior work by u/TimAndTimi and u/Reddactor's blog series, and details the hardware and model specs.
A user shares a reference setup for running DeepSeek-V4-Flash-0731 on a single NVIDIA GH200 using DSpark and UVA offload, since the 284B MoE model does not fit in 144GB HBM. The post credits prior work by u/TimAndTimi and u/Reddactor's blog series, and details the hardware and model specs.
A Reddit user shares a llama.cpp configuration tip: instead of using --no-mmproj-offload to save VRAM, which is slow, users can dedicate a secondary low-VRAM GPU to the vision projector (mmproj) with --mmdev. This keeps inference speed unaffected while making vision processing roughly an order of magnitude faster, especially useful for agentic coding workflows.
A Reddit user shares a llama.cpp configuration tip: instead of using --no-mmproj-offload to save VRAM, which is slow, users can dedicate a secondary low-VRAM GPU to the vision projector (mmproj) with --mmdev. This keeps inference speed unaffected while making vision processing roughly an order of magnitude faster, especially useful for agentic coding workflows.
Community tests show Ling-3.0-flash INT4 on a single DGX Spark can be nearly doubled in speed from 20.8 to 38.7 tok/s by disabling eager execution and enabling MTP speculative decoding. A separate run generated 15,128 tokens in one response at a steady 35.68 tok/s, demonstrating sustained throughput for local inference.
Community tests show Ling-3.0-flash INT4 on a single DGX Spark can be nearly doubled in speed from 20.8 to 38.7 tok/s by disabling eager execution and enabling MTP speculative decoding. A separate run generated 15,128 tokens in one response at a steady 35.68 tok/s, demonstrating sustained throughput for local inference.