A developer released llamAmpere, a custom llama.cpp fork optimized for Ampere-architecture GPUs, alongside a Qwen3.8-27B GGUF quant on Hugging Face. The recommended configuration reaches 90+ tokens/second through 100K context (up to 240K) on a single RTX 3090, which the author says exceeds API speeds for 27B models and significantly improves local LLM utility on 30-series cards.
A Reddit user repurposed four 8GB RTX 3060 Ti cards from an old crypto rig into a local inference setup, avoiding a costly GPU upgrade. Using tensor parallelism via vLLM with the HyperQwen Ampere fork, they run Swift-Qwen3.8-27B at ~120 t/s with 150k context at bf16, or full 262k context at ~70 t/s with kv8 quantization. The post is a practical guide for budget multi-GPU local serving.
A Reddit user repurposed four 8GB RTX 3060 Ti cards from an old crypto rig into a local inference setup, avoiding a costly GPU upgrade. Using tensor parallelism via vLLM with the HyperQwen Ampere fork, they run Swift-Qwen3.8-27B at ~120 t/s with 150k context at bf16, or full 262k context at ~70 t/s with kv8 quantization. The post is a practical guide for budget multi-GPU local serving.
Developer JakeATX released LlamAmpere v0.4, a Llama.cpp fork with Ampere-specific optimizations, achieving 95+ tokens/second over 100K generated tokens for a Qwen3.8 27B model at 262K context on one RTX 3090. The update delivers ~10% speed gains and 10%+ more max context versus the prior version, with vLLM as the closest competing runtime. The author also quantifies the quality cost of the TQ5/TQ4 KV cache quantization used.
Developer JakeATX released LlamAmpere v0.4, a Llama.cpp fork with Ampere-specific optimizations, achieving 95+ tokens/second over 100K generated tokens for a Qwen3.8 27B model at 262K context on one RTX 3090. The update delivers ~10% speed gains and 10%+ more max context versus the prior version, with vLLM as the closest competing runtime. The author also quantifies the quality cost of the TQ5/TQ4 KV cache quantization used.
A community recipe and repo for running Qwen3.8-Flash-Next on a single DGX Spark (GB10) device. It combines Intel AutoRound int4 quantization with additional uncalibrated int8/fp8 quantization of specific layers, served via vLLM with an fp8 ngram table offloaded to SSD or an RDMA server. It lets local-LLM hobbyists fit the model on constrained hardware at usable speeds.
A community recipe and repo for running Qwen3.8-Flash-Next on a single DGX Spark (GB10) device. It combines Intel AutoRound int4 quantization with additional uncalibrated int8/fp8 quantization of specific layers, served via vLLM with an fp8 ngram table offloaded to SSD or an RDMA server. It lets local-LLM hobbyists fit the model on constrained hardware at usable speeds.
A Reddit user asks what determines local LLM speed, listing token efficiency, token speed, and prefill as factors. The discussion centers on hardware and model selection for running models like Qwen 3.8 27b on a 4090.
A Reddit user asks what determines local LLM speed, listing token efficiency, token speed, and prefill as factors. The discussion centers on hardware and model selection for running models like Qwen 3.8 27b on a 4090.
A Reddit user reports achieving 80 tok/s burst speed running Unsloth's Qwen3.6:35B UD Q4_K_M quantized model with 100k context on a single Nvidia P40 (24GB) using TheTom's TurboQuant fork of llama.cpp. The setup disables reasoning to avoid thinking loops and omits the vision component to save memory.
A Reddit user reports achieving 80 tok/s burst speed running Unsloth's Qwen3.6:35B UD Q4_K_M quantized model with 100k context on a single Nvidia P40 (24GB) using TheTom's TurboQuant fork of llama.cpp. The setup disables reasoning to avoid thinking loops and omits the vision component to save memory.