Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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 Aufrufe • vor 5 Monaten •via X (Twitter)

43 Kommentare

Profilbild von NotYourDC
NotYourDCvor 5 Monaten

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?

Profilbild von leopardracer
leopardracervor 5 Monaten

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

Profilbild von starmex
starmexvor 5 Monaten

cut the wrappers, run the source. solid setup

Profilbild von leopardracer
leopardracervor 5 Monaten

exactly the mindset

Profilbild von elune
elunevor 5 Monaten

zero api fees forever wins

Profilbild von leopardracer
leopardracervor 5 Monaten

@asakura0x correct conclusion👍🏻

Profilbild von elune
elunevor 5 Monaten

😼

Profilbild von Samuel Gregory
Samuel Gregoryvor 5 Monaten

Thank you but I'm not American

Profilbild von leopardracer
leopardracervor 5 Monaten

sorry 🙏🏽

Profilbild von 𝔸𝕟𝕕𝕚 𝕁𝕒𝕖𝕘𝕖𝕣📯📸
𝔸𝕟𝕕𝕚 𝕁𝕒𝕖𝕘𝕖𝕣📯📸vor 5 Monaten

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

Profilbild von kkiran
kkiranvor 5 Monaten

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

Profilbild von Ghost Signal
Ghost Signalvor 5 Monaten

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.

Profilbild von Kekko D’Amato
Kekko D’Amatovor 5 Monaten

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

Profilbild von kfant
kfantvor 5 Monaten

who is this guy ? credit/reference

Profilbild von Bill The Radio Guy
Bill The Radio Guyvor 5 Monaten

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.

Profilbild von Joseph Hurtado - Founder Granata Consulting
Joseph Hurtado - Founder Granata Consultingvor 5 Monaten

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

Profilbild von slash1s
slash1svor 5 Monaten

yep definitely need to save this..

Profilbild von leopardracer
leopardracervor 5 Monaten

230 people already did

Profilbild von I Pun Daddy
I Pun Daddyvor 5 Monaten

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

Profilbild von CoreAI
CoreAIvor 5 Monaten

No api fees👏

Profilbild von Bober_smart
Bober_smartvor 5 Monaten

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

Profilbild von leopardracer
leopardracervor 5 Monaten

once you start you don’t go back

Profilbild von Mario 🐧
Mario 🐧vor 5 Monaten

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.

Profilbild von b
bvor 5 Monaten

😁 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 🤦‍♂️

Profilbild von Gipp 🦅
Gipp 🦅vor 5 Monaten

In fact, with AI it's very easy

Profilbild von leopardracer
leopardracervor 5 Monaten

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

Profilbild von Insomnia
Insomniavor 5 Monaten

he know facts how it's all works

Profilbild von leopardracer
leopardracervor 5 Monaten

no theory. just what actually runs

Profilbild von xpost
xpostvor 5 Monaten

@grok is this real setup, Worth duplicating?

Profilbild von Victoria Neiman
Victoria Neimanvor 5 Monaten

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:

Profilbild von Blak
Blakvor 5 Monaten

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!

Profilbild von Daily Story
Daily Storyvor 5 Monaten

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

Profilbild von Jeff Davis, MD
Jeff Davis, MDvor 5 Monaten

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

Profilbild von Kyle
Kylevor 5 Monaten

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

Profilbild von Thirty
Thirtyvor 5 Monaten

@grok solid or no? Risk involved?

Profilbild von 84動物農場🇺🇦
84動物農場🇺🇦vor 5 Monaten

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.

Profilbild von Horoshi⚡
Horoshi⚡vor 5 Monaten

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

Profilbild von TruthSeeker
TruthSeekervor 5 Monaten

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

Profilbild von whiletrue111
whiletrue111vor 5 Monaten

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

Profilbild von James Rogers - Cinematographer; Truth@24fps
James Rogers - Cinematographer; Truth@24fpsvor 5 Monaten

Today in “duh”

Profilbild von AX⚡
AX⚡vor 5 Monaten

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

Profilbild von Tony Scott 🧄(🦆🐓🐵🧪🧬🪪)❌=↑🧄🧄🧄🥩🥚🧀↓👽👾🤖
Tony Scott 🧄(🦆🐓🐵🧪🧬🪪)❌=↑🧄🧄🧄🥩🥚🧀↓👽👾🤖vor 5 Monaten

@grok summarise the video.

Profilbild von StarShipX
StarShipXvor 5 Monaten

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

Ähnliche Videos

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 Aufrufe • vor 4 Monaten