正在加载视频...

视频加载失败

THIS AMERICAN DEVELOPER SPENT WEEKS DEBUGGING TIMEOUT ERRORS IN OLLAMA. THEN HE LOOKED UNDER THE HOOD LM Studio is just llama.cpp Ollama is just llama.cpp so he cloned llama.cpp from source, pulled Qwen 3.6 35B off Hugging Face, set up asymmetric KV quantization and got a local server running...

241,145 次观看 • 5 个月前 •via X (Twitter)

43 条评论

NotYourDC 的头像
NotYourDC5 个月前

Who is speaking in this video? Is that you? It's not an American he is clearly English. Bit confused by the video and the link to 2-GPU build below it. How are they related?

leopardracer 的头像
leopardracer5 个月前

this developer figured out the same thing I wrote about: strip the wrappers, run llama.cpp raw. different hardware, same conclusion

starmex 的头像
starmex5 个月前

cut the wrappers, run the source. solid setup

leopardracer 的头像
leopardracer5 个月前

exactly the mindset

elune 的头像
elune5 个月前

zero api fees forever wins

leopardracer 的头像
leopardracer5 个月前

@asakura0x correct conclusion👍🏻

elune 的头像
elune5 个月前

😼

Samuel Gregory 的头像
Samuel Gregory5 个月前

Thank you but I'm not American

leopardracer 的头像
leopardracer5 个月前

sorry 🙏🏽

𝔸𝕟𝕕𝕚 𝕁𝕒𝕖𝕘𝕖𝕣📯📸 的头像
𝔸𝕟𝕕𝕚 𝕁𝕒𝕖𝕘𝕖𝕣📯📸5 个月前

This llama launcher gives us full control how llama-server is executed

kkiran 的头像
kkiran5 个月前

Please link others videos to the source with your commentary. Thank you! @0x5am5 thanks for the contribution!

Ghost Signal 的头像
Ghost Signal5 个月前

Most developers debug the wrapper. Never the engine. LM Studio. Ollama. Different names. Same llama.cpp underneath. The timeout wasn’t a bug. It was a layer you didn’t need. Going direct to llama.cpp isn’t advanced. It’s just removing the abstraction that was hiding the problem. 53 tok/s. 262K context. Zero fees. That’s what’s under the hood.

Kekko D’Amato 的头像
Kekko D’Amato5 个月前

the asymmetric KV quantization bit is what really matters here. most people don't realize that KV cache is the memory bottleneck on consumer GPUs, not weights. Q8 weights + Q4 KV cache is a genuinely different tradeoff than Ollama's defaults, and going direct llama.cpp lets you tune that knob. the wrappers abstract away exactly the setting you'd want to change

kfant 的头像
kfant5 个月前

who is this guy ? credit/reference

Bill The Radio Guy 的头像
Bill The Radio Guy5 个月前

Or just configure lm studio to run the tool correctly, it has tons of configuration options and surely more could be added if that were necessary.

Joseph Hurtado - Founder Granata Consulting 的头像
Joseph Hurtado - Founder Granata Consulting5 个月前

Thanks for the article. Can you share the link to the source video? Like you, that fellow deserves a follow.

slash1s 的头像
slash1s5 个月前

yep definitely need to save this..

leopardracer 的头像
leopardracer5 个月前

230 people already did

I Pun Daddy 的头像
I Pun Daddy5 个月前

Classic move: abstract the abstraction, then debug the original abstraction.

CoreAI 的头像
CoreAI5 个月前

No api fees👏

Bober_smart 的头像
Bober_smart5 个月前

I'm starting to watch it, it sounds very tempting

leopardracer 的头像
leopardracer5 个月前

once you start you don’t go back

Mario 🐧 的头像
Mario 🐧5 个月前

I have a homogeneous GPU set up. 5060ti and 3060 ~ 28.5 gb's. Can meaningfully run qwen 27/35b My Thoughts: - heterogeneous is better(same gpu arch) - You'll want higher mem-bandwidth - Can run a model for workflows locally, but still want to build with a SOTA model.

b 的头像
b5 个月前

😁 so it took this idiot (and also you) 3 years to understand ollama was just llama.cpp under the hood. Great job keep it up 🤦‍♂️

Gipp 🦅 的头像
Gipp 🦅5 个月前

In fact, with AI it's very easy

leopardracer 的头像
leopardracer5 个月前

easy once you know the stack. that’s the whole point of the article

Insomnia 的头像
Insomnia5 个月前

he know facts how it's all works

leopardracer 的头像
leopardracer5 个月前

no theory. just what actually runs

xpost 的头像
xpost5 个月前

@grok is this real setup, Worth duplicating?

Victoria Neiman 的头像
Victoria Neiman5 个月前

struck the OpenAI bill with 2 GPUs. not showing off, this is a business model. platform prices can change anytime. your hardware can't. more context:

Blak 的头像
Blak5 个月前

but how do you solve the hardcoded 2GB metabuffer ?the server will crash when >2GB! so llama.cpp you will not be able to run as a 24/7 server with 120k context ! im testing now for weeks for stable 24/7 server inference for lokal production! please share with us the code!

Daily Story 的头像
Daily Story5 个月前

Building locally seems like a game changer for overcoming those timeout errors!

Jeff Davis, MD 的头像
Jeff Davis, MD5 个月前

Credit need to go to @0x5am5 and the original video:

Kyle 的头像
Kyle5 个月前

Qwen 3.6 35B from Huggingface is 72gb... So this story is bullshit right off the bat.

Thirty 的头像
Thirty5 个月前

@grok solid or no? Risk involved?

84動物農場🇺🇦 的头像
84動物農場🇺🇦5 个月前

I have an almost identical experimental machine with dual 4080S graphics cards. I always cram it with the largest model that can run, but it seems this isn't the best approach. Thanks for the experiment.

Horoshi⚡ 的头像
Horoshi⚡5 个月前

🤣This happens too, I thought for a long time...🤷

TruthSeeker 的头像
TruthSeeker5 个月前

Check out TurboAgent. It does the weights and KV compression.

whiletrue111 的头像
whiletrue1115 个月前

And what is all of this for? What is he actually doing with this? Summarizing articles every morning?

James Rogers - Cinematographer; Truth@24fps 的头像
James Rogers - Cinematographer; Truth@24fps5 个月前

Today in “duh”

AX⚡ 的头像
AX⚡5 个月前

lmao yeah no shit it's all llama.cpp, what else would it be? hahaha

Tony Scott 🧄(🦆🐓🐵🧪🧬🪪)❌=↑🧄🧄🧄🥩🥚🧀↓👽👾🤖 的头像
Tony Scott 🧄(🦆🐓🐵🧪🧬🪪)❌=↑🧄🧄🧄🥩🥚🧀↓👽👾🤖5 个月前

@grok summarise the video.

StarShipX 的头像
StarShipX5 个月前

すごい技術ですね、私も試してみたいです。

相关视频

six months ago this wasn't happening on 8gb vram. running unsloth's Q4_K_XL quant of gemma 4 26b-a4b-it-qat, a sparse MoE model with only 4b active params on a single rtx 4060 laptop gpu, 8gb vram, 20+ tok/s decode. no cloud, no api, no offload hacks. just a gaming laptop on battery. what makes it fit: google's QAT (quantization aware training), plus MTP (multi token prediction) support in the latest llama.cpp builds. that combo is the single biggest unlock for local inference on low vram. rtx 3060, rtx 3070, gtx 1070, gtx 1080, rtx 4050, rtx 4060, rtx 5050, rtx 5060 — any 6-8gb consumer gpu, old or new — this model runs on it. world cup season, so i told it to build a soccer themed flappy bird clone. one shot, zero iteration, fully playable. six months ago an 8gb model could barely clone vanilla flappy bird. now it's shipping a themed game from a sparse MoE model running locally on a laptop battery. inference benchmarks: - decode throughput: 30 tok/s - context: 64k. this is the real unlock. 64k ctx is what makes a hermes agent loop viable locally on this model, not just single-turn chat. llama.cpp flags: -m gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf -c 64000 -cmoe --port 8080 game's deployed on my own site, built and shipped end to end with open source llm, zero closed source api dependency in the pipeline. link in the description. gguf weights on huggingface, link in the comments. pull it down, run it on whatever 8gb card is sitting in your rig. try the game and tell me your score and what you want in v2. local llms on consumer gpus stopped being a meme.

Alok

62,381 次观看 • 4 个月前