The author ran Qwen3.8-27B locally using DeepSeek Harness, achieving fast inference and saving over $650 compared to API costs for equivalent workloads.
I've been experimenting with Qwen3.8-27B using DeepSeek Harness. It's a monster at long-horizon tasks, and the results were pretty wild. DeepSeek Harness ran on my Windows PC and connected over LAN to NInfer on a separate RTX PRO 6000 box. The model was Qwen3.8-27B with a 262K context window. All shell commands and file operations stayed on the client PC. The server did nothing except inference. The quant was NInfer's groupwise-int artifact, which uses a mixed Q4/Q5/Q6 allocation. I plan to try the NVFP4 profile that NInfer supports next. The 8+ hour run 966 model calls 130.2M task input tokens and 812.5K output tokens 131.2M input and 853.3K output after including compaction 972 model-facing tool calls 1,421 actual local tool operations 31 automatic compaction attempts 104.83 output tok/s weighted decode speed Zero model-generation failures The context sizes got huge. The median root request was 136.6K tokens, p95 was 205.9K, and the largest was 231.2K. The harness pushed about 160 input tokens for every output token. No surprise that repeated context became the main workload. The fun part is that generation itself was fast. Dividing the logical input by total time to first token gives about 12.4K prompt tok/s for the root and 8.5K across the root plus subagent. That is not raw GPU PP/s because it includes queue time and possibly reused prefixes, but it is still useful as a client-side number. Root time to first token had a median of 0.8 seconds but a p95 of 136 seconds. The subagent's median was 151 seconds, while its median decode phase was only 5.3 seconds. Once NInfer got a request onto the GPU, it absolutely flew. Running two agents against one endpoint mostly added queueing and prefill contention. The 1,421 local operations included 576 PowerShell calls, 259 reads, 221 edits, 161 writes, and 114 searches. Only 30 failed, giving the local tool layer a 2.11% error rate. The file tools were mostly finishing in milliseconds. What would this have cost through APIs? The local run had no token bill, but I priced the full 131.2M input and 853.3K output workload using current API rates without cache discounts. Model Estimated API cost DeepSeek V4 Flash $18.61 GPT-5.6 Luna $27.26 Claude Sonnet 5 $270.93 Claude Opus 4.6 $677.32 Pricing references: DeepSeek, OpenAI, Sonnet 5, and Opus 4.6. This is crazy. I know the costs aren't perfect with DS V4 Flash 0731 hitting cahce a lot and such, but still. It was cranking out roughly 105 tok/s. The problems were repeated six-figure prompts, prefill, and two agents competing over one inference endpoint. It feels like I made money today. Crazy that it reached the end goal without a single model-generation failure.
User demonstrates Qwen 3.6 27B/35B running locally with llama-server cuts Claude Code API costs from $142 to <$4 for 8-hour vibe-coding session, achieving 30-day payback on $4500 dual-RTX 3090 rig.
Qwen 3.6 27B scored 2% on the DeepSWE benchmark, placing 18/20 above Haiku 4.5 and Minimax M2.7, highlighting the gap between local and leading-edge models.
A user shares positive experiences using the Qwen 3.8 27b model with DeepSeek Harness, praising its stability and long-context handling, but mentions speed limitations and hopes for future model releases.
Qwen 3.8 27b, a sub-30 billion parameter AI model, has been released and is suitable for local inference on consumer hardware like RTX 3090 or M4 Pro, potentially replacing cloud-based AI subscriptions and shifting workflows locally.
Running the Qwen 3.8 27b model with vision on a single RTX 3090 GPU enables 150k context length, and integration with DeepSeek harness allows for plugin development, though a search engine plugin caused a system crash.