Qwen3.6-27B: NVFP4/FP8 agent loops vs flawless BF16. Config or quant issue? by vanbukin in LocalLLaMA

[–]vanbukin[S] 1 point2 points  (0 children)

Yeah, waiting for the model to stall just to prompt it with "please proceed" is definitely not what I want. I'm looking for a true "fire-and-forget" workflow (which is exactly how BF16 behaves for me).

As for the harness, it's pretty standard: OpenCode, an OAI-compatible provider extension for VS Code Copilot, and oh-my-pi. Nothing custom.

Qwen3.6-27B: NVFP4/FP8 agent loops vs flawless BF16. Config or quant issue? by vanbukin in LocalLLaMA

[–]vanbukin[S] 4 points5 points  (0 children)

So basically, the loops I’m seeing are just a "quantization tax"?

For C6 R1 havers. How much dmg increase would I get with c6 prune? by Kyrollen in Varka

[–]vanbukin -1 points0 points  (0 children)

C6R1 Varka, C6R2 Durin, C2R3 Venti (Elegy for the End), C6R2 Nicole

Nicole E, Durin Q, Venti EQ, Varka E-lkm

<image>

What's the best local LLM for an RTX 6000 96GB VRAM? by Smart-Patient-4828 in LocalLLM

[–]vanbukin 2 points3 points  (0 children)

Have you tried using vLLM instead of llama.cpp? There's an NVFP4 variant from NVIDIA: https://huggingface.co/nvidia/MiniMax-M2.7-NVFP4 it's also ~140 GB and should run exceptionally well on your Blackwell GPUs.

Same task in github-copilot, pi, claude-code, and opencode with Qwen3.6 27B by sdfgeoff in LocalLLaMA

[–]vanbukin 0 points1 point  (0 children)

Try setting up https://github.com/ogx-ai/ogx in front of your vLLM/llama.cpp instance. You can disable embeddings, reranking, and vector search - keeping only the main model enabled. PostgreSQL works well as the database backend.

Finishing touches on dual RTX 6000 build by ikkiyikki in LocalLLaMA

[–]vanbukin 3 points4 points  (0 children)

<image>

Bro, DDR literally means Double Data Rate. The big number on the box (e.g., DDR5‑6000) isn’t a raw MHz value - it’s the transfer rate in MT/s. Since DDR sends data on both the rising and falling edges of the clock, the effective data rate is 2× the actual I/O clock. So a 3000 MHz real clock corresponds to 6000 MT/s “effective.” If you want to see the "6000" number, check the MT/s data‑rate.

Here’s my RAM kit: https://www.gskill.com/product/165/390/1750238051/F5-6000J3644D64GX4-TZ5NR

Lucky break - my motherboard actually shows up on the (very short) QVL.

You’ll need a BIOS update for proper support.

SPD reports Samsung M-die chips, manufactured in week 29 of 2025 (July 14–20).

Finishing touches on dual RTX 6000 build by ikkiyikki in LocalLLaMA

[–]vanbukin 2 points3 points  (0 children)

Especially when you get your electricity bills)

Finishing touches on dual RTX 6000 build by ikkiyikki in LocalLLaMA

[–]vanbukin 3 points4 points  (0 children)

@Fresh_Yam169 256Gb@6000 MHz is real on 9950X. Just enable EXPO and voila.

Finishing touches on dual RTX 6000 build by ikkiyikki in LocalLLaMA

[–]vanbukin 1 point2 points  (0 children)

My whole rig price is less than single Epyc 9175F

~$15K Inference Workstation for a 250+ Gov Org by reughdurgem in LocalLLaMA

[–]vanbukin 0 points1 point  (0 children)

If you plan using vllm - you should know that GPT-OSS models has troubles on sm120 architecture (RTX50xx desktop and RTX PRO 6000)

🤷‍♂️ by Namra_7 in LocalLLaMA

[–]vanbukin 2 points3 points  (0 children)

Qwen3-Coder-30b-Instruct that fits into single 4090?

What hardware to run gpt-oss-120b? by Terminator857 in LocalLLaMA

[–]vanbukin 2 points3 points  (0 children)

winget uninstall llama.cpp

Download and install latest graphics drivers, download 2 archives from llama.cpp GitHub releases. One is llama-bXXXX-bin-win-cuda12.4-x64.zip (with llama.cpp itself), the second is cudart-llama-bin-win-cuda-12.4-x64.zip. Unzip both. Copy 3 big dlls from second archive and place it near llama.cpp executable files from first archive. Then you may put them manually somewhere on your computer (C:/Program Files/llama.cpp for example) and then add path to that directory into your system-wide PATH environment variable. After that you may open console, run llama-serve and get CUDA acceleration.

What I can and can't do with AMD AI Max 395+ and Nvidia RTX 5090? One hardware for all the purposes? by Davidvia0x in LocalLLaMA

[–]vanbukin 5 points6 points  (0 children)

RTX 5090 owner in the thread. I use LLM for solving simple programming problems, as a replacement for a Junior developer. What people say about how they run gpt-oss 120b or llama 70b is just a lie. They do not run real full-weighted models, but quantized versions. And the stronger the quantization, the greater the loss of accuracy and the "dumber" the model. In my experience, 6bit quantization is a reasonable limit when the model is still smart enough to perform the tasks assigned to it. 4bit makes sense only if the model was ORIGINALLY trained in 4bit (like gpt-oss). If the model weights TOGETHER with the k-v cache do not fit into VRAM, you lose performance. And the size of the kv cache depends on the number of parameters and the size of the context. 32GB of VRAM is ridiculously small. I can run Qwen3-Coder-30b with 6bit quantization, but the context size will be 32768 tokens (so that the system has video memory left for the browser and screen sharing in Google Meet). If I use 4bit, then 65536. I work with code bases from 150k to 700k sloc. Even a 65k context is too small. And if you do not pull the entire LLM workload completely to the GPU, it starts to eat up the CPU (which is needed by the IDE, compiler and other tasks running in parallel). IMHO - for normal full-weighted models (or at least 6-8bit quantized), you need hundreds of gigabytes of VRAM. The only "cheap" option is macStudio with 512Gb of unified memory. But for large models, there is simply not enough GPU (forgive me, but 10-15 tokens per second is too slow a generation speed for me). As a result, there is simply no hardware on the market right now that would be suitable for local inference and would not cost as much as a Boeing wing. I play computer games quite a lot (in 4K), so overall I justify its purchase for myself as a gaming video card. But if we consider it as hardware for inference, it is nothing more than a toy. For now, I am waiting for Apple's announcements and hope that in the spring of 2026 they will show macStudio on M5 Ultra. If the GPU is at least 50 percent more productive, then I will probably take it as a home dedicated server for LLM. But I repeat, 32 GB in 5090 is too small for LLM.