AI systems, Local LLMs, Agents, GPUs I test models, read code, and post the numbers. Programmer / DJ

Seoul, KR
Joined September 2013
I happily picked up two used Nvidia Tesla P40 GPUs. I knew the P40 was old and ridiculously overbuilt. What I did not expect was how long the GPUs would become once the coolers were attached. Tried putting them in the case. Nope. The cooler end would not fit. I thought about it for about 10 seconds. Turns out the bottleneck was not the human. It was the case. So I grabbed a hammer and pliers and destroyed the front section of the case. After that both P40 GPUs fit perfectly. Put the cover back on and you cannot even tell from the outside. Apparently hardware fits if you hit it hard enough. Good experience.
6
2
2
24
8,393
MiMo-V2.6 Pro w/ 8x DGX Sparks Concurrency 1 Decode TPS : 40 tps - Where is the limit to DGX Spark's performance? It’s only natural that the price keeps climbing.
DGX Spark x8 Cluster : XiaomiMiMo/MiMo-V2.6-Pro-MOPD C1 : 40 tok/s C2 : 62 tok/s C4 : 82 tok/s vLLM: eugr's spark-vllm-docker(nVIDIA official) This is the smartest model I’ve run on DGX Spark so far. Zero benchmark failures!!!💯 Not a single one🔥
7
LFM3 1.7B Uncensored by AtomicChat @atomic_chat_hq has an uncensored GGUF build of Liquid AI's LFM3 1.7B. The original model uses a hybrid architecture with convolution and attention layers. It supports a 256K context window and is designed for lightweight local agents, tool calling, and structured outputs. At 4 bit precision, the original model needs roughly 1GB for its weights. That makes it practical for laptops and even mobile devices. The uncensored version adds another option for local inference with fewer content restrictions. huggingface.co/AtomicChat/LF…
24
Ouroboros: Zero-Dependency Single-File Rust GPU Compiler & Quantized LLM Engine An old laptop GPU with just 2GB of VRAM is apparently outperforming an RTX 4060 in a specific LLM decode benchmark. Ouroboros runs the 3B parameter Llama model on a GeForce MX150 using custom 2 bit GPU kernels written in pure Rust. The developer reports 0.517ms on the MX150 versus 0.796ms on the RTX 4060 at 4096x4096. That is 1.54 times faster in this test despite using different precision levels. No CUDA toolkit, no PyTorch, and no external Rust crates. Just a single Rust source file that generates GPU machine code. The same project reportedly reaches 23.35 TFLOPS on an A100 80GB. Not bad for a laptop GPU most people retired years ago. github.com/gkjuwon-tech/ouro…
26
LFM3 Liquid AI has released LFM3, six open weight models around 2B parameters. LFM3-1.7B for text, LFM3-VL-2B for vision, LFM3-Audio-2B for speech in 18 languages, LFM3-Omni-2B, plus the d1-2B and d1-Omni-2B decision models. All share a tri-hybrid 24 layer base with 13 conv, 5 sliding window and 6 global attention layers. 256K context and around 1GB at 4 bit. Liquid claims 1.8 to 2.8x faster decoding than rivals. GGUF, MLX, ONNX and FP8 builds ship under LFM Open License v1.0. LFM3-1.7B: Text model huggingface.co/LiquidAI/LFM3… LFM3-VL-2B: Vision model huggingface.co/LiquidAI/LFM3… LFM3-Audio-2B: Speech model huggingface.co/LiquidAI/LFM3… LFM3-Omni-2B: Omni model huggingface.co/LiquidAI/LFM3… d1-2B: Decision model huggingface.co/LiquidAI/d1-2… d1-Omni-2B: Omni decision model huggingface.co/LiquidAI/d1-O…
5
261
Strata Strata 0.2.7 is out with some meaningful improvements for local AI inference. On an RTX 3060 12 GB, Qwen3.8 Flash Next code generation improved by 37 percent in the developer tests. DeepSeek V4.1 Flash now supports Windows systems with Ryzen AI Max processors. The biggest surprise is dual GPU performance. Two RTX A4000 cards reduced first token latency for a 32K prompt from 141.8 seconds to just 27.7 seconds. It also brings a better web chat interface and larger context options for DeepSeek. github.com/Niko1221/Strata
123
Ling 3.1 Flash 1019 InclusionAI has released Ling 3.1 Flash 1019 weights on Hugging Face. It keeps 560B total parameters, 25B active per token, and an advertised 1 million token context window. The update focuses on post training improvements rather than increasing model size. The Artificial Analysis Intelligence Index moves from 41 to 44. AA Briefcase climbs from around 1400 to 1524 Elo, while AutomationBench AA improves from 62 to 68 percent. Those are meaningful gains for agent workflows. huggingface.co/inclusionAI/L…
76
Strata DualGPU Strata DualGPU makes two different NVIDIA GPUs work together on a PC with just 32 GB of RAM. Using an RTX 5080 and RTX 4060 Ti, the developer reports code generation jumping from 29 to 143 tokens per second on Qwen3.8 Flash Next. The trick is keeping experts in VRAM and RAM while pipelining decoding across both GPUs instead of leaving one idle. A fine tuned draft layer pushes that to 161 tokens per second. github.com/Hardin22/Strata-D…
13
23
6
221
11,671
Ninfer KVMem Async Ninfer KVMem Async is making long context local inference more practical on consumer GPUs. It runs a quantized 27B model with a 256K logical context on an RTX 5080 with 16GB VRAM by offloading KV cache pages to system RAM. The interesting part is the async page pipeline. It overlaps memory transfers with decoding instead of making the GPU wait for pages. The author reports decode speed improving from 188 to 235 tokens per second in deep multi turn tests. The deepest segment showed nearly 2 times the performance. github.com/paicat1/Ninfer-KV…
72
TensorFold TensorFold 1.1.6 is tackling one of the more annoying parts of local LLM inference. According to the release tests, eight concurrent Qwen3.8 27B chats sharing a new 28k token system prompt on GB10 saw the last request reach its first token in 31 seconds instead of 201 seconds. On an M3 Ultra, evicted conversations can now resume from disk in 2.6 seconds instead of 56 seconds. Metal also keeps decoding streams moving while longer prompts are processed. Less waiting without changing the generated tokens. github.com/ashhart/TensorFol…
2
88
Mac mini M4 running Qwen3.5 9B at 4 bit. mlx lm gets 19.3 tokens per second, oMLX 20.8, and Rapid MLX 20.0. Ollama reaches 17.0. Enable MTP on Rapid MLX and it jumps to 29.4 tokens per second. A 47 percent boost on the same hardware. Meanwhile, all engines still spend around 40 seconds processing an 8K prompt. MTP wins on decode.
前两天看到,M5 Max 跑 Qwen3.5-9B 能到 115 tok/s。手边只有一台 Mac mini M4 24GB,就想看看普通机器上是什么情况,顺手把常见的几个引擎都测了一遍。 模型统一用 Qwen3.5-9B 4-bit,思考模式全关,每次让它写 256 个 token。 先说短问题的生成速度 mlx-lm 19.3 tps,oMLX 20.8 tps,Rapid-MLX 20.0 tps,Ollama 17.0 tps。说实话,差别没我想的大,几个 MLX 引擎基本是一个水平。 接着把 Rapid-MLX 的 MTP 打开,其他什么都没动,直接到了 29.4 tps,快了将近一半。丢一篇 8K 的长文进去,也还是 29 左右,速度没掉。 MTP 是 Multi-Token Prediction,多 token 预测。普通生成是一个 token 一个 token 往外蹦,每蹦一个,模型都要把全部权重从内存里读一遍。M4 的内存带宽只有 120GB/s,9B 的权重大约 5.4GB,算下来一秒最多二十来个,这也是为什么几个引擎都卡在 20 左右。 MTP 给模型配了一个很小的"预测头",先一口气猜后面两三个 token,再让主模型一次性核对。猜对的直接收下,猜错的从错的地方重来。只要猜得够准,读一次权重就能吐出好几个 token,速度自然就上去了。 对照一下 M5 Max:它开 MTP 是从 80 到 115,涨了 44%;M4 是从 20 到 29.4,涨了 47%。比例差不多,所以这个加速不是新芯片专属,小机器一样用得上。 长文本就是另一回事了,真正的等待在"读题"。 8K token 的输入丢进去,所有引擎都要先花 36 到 42 秒把整段输入读完(prefill),然后才出第一个字。M4 一秒大约读 190 到 220 个 token,这一步拼的是芯片算力,跟用哪个引擎关系不大,MTP 也帮不上。 所以在小机器上,短问短答、改写一句话、回一封短邮件都很顺;把一整篇长文档丢进去,就得先等半分钟以上。 补充两点:Ollama 用的是 GGUF 格式,跟 MLX 的 4-bit 不完全一样,只能当参考;测的时候后台还开着别的东西,数字可能偏保守一点。 你的 Mac 跑出来是多少?可以在评论里贴一下芯片、内存、用的引擎和速度,我攒一张表出来。
6
12
1,163
dextune retweeted
If you have spare RAM, increase --conversation-cache for Strata now. With 64GB RAM, I cached 32 conversations. Token use doubled vs. yesterday, but power draw fell 30%—so energy cost per token dropped to 35% of yesterday’s, a 65% saving. That matters for local LLMs.
9
10
194
9,237
Strata w/ RTX 5080 + DDR5 64GB Qwen3.8 Flash Next 256k ctx 70~100 tps - He was running Qwen3.8-27B at a 98K context window with speeds of 60 tps. With Strata's hybrid offloading, he achieved 70 to 100 tps at a 256k context window. If you have sufficient system RAM, it is a smart choice.
Replying to @Oluwaphilemon1
Bro i was running qwen 3.8 27b locally using llama.cpp (ggml fork) and was getting 60 t/s with 98k context and then i start experimenting with Strata Inference and now i,m able to run run qwen 3.8 flash next 125B using hybrid offloading with 256k ctx at whooping 70 to 100 t/s 😅
1
3
15
2,532
NovaMLX NovaMLX takes a different approach to local AI on Apple Silicon. It is a Swift based LLM and VLM server, but the interesting part is TIE, its MoE aware SSD streaming engine. Instead of requiring the entire model in unified memory, it keeps active weights in memory and loads the rest from disk. The README claims it can run a 141GB DeepSeek V4 Flash model and even a 779GB V4 Pro model on a 128GB Mac. It also supports over 50 model families and provides OpenAI and Anthropic compatible APIs. github.com/cnshsliu/novamlx
1
9
1
46
2,930
Atria Dawn Shanghai AI Lab has released Atria Dawn, an open weight agentic model built on the 744B parameter GLM 5.2 MoE architecture. The full release doubles the context window from 256K to 512K tokens. It focuses on research, coding, tool use, automated experiments, and producing verifiable results. The team reports 96.5 on DeepSearchQA, 78.4 on BFCL v4, and 88.2 on MLE Bench Lite. modelscope.ai/models/Shangha…
1
12
1,761
Strata w/ RTX 3090 + RTX 3080 Ti 80GB DDR4 RAM Qwen 3.8 Flash Next IQ3_S (Local) Local LLM vs. ZAI API Qwen3.8-Flash-Next (Local) Decode TPS : 113.3 tps GLM-5.3-Flash (ZAI API) Decode TPS : 54.4 tps
qwen 3.8 flash next iq3_s, sur mes deux cartes, 3090 et 3080 Ti + 80gb DDR4, avec Strata en local face à glm-5.3-flash, via l'api payante chez zai mme prompt : le bureau homelab de nuit avec timelapse 24h et animation du soleil 113,3 tok/s contre 54,4 en decode: Qwen en local gagne (mauvais jour pour 5.3-flash) 474,7 s de mon côté contre 701,3 pour l'api les deux rendus sont sortis ok, à ce rythme qwen 4 flash next remplacera mes abonnements cloud quand il sortira
1
3
27
2,478
Qwen3.8-27B w/ M5 Max M5 Max 36GB Rapid-MLX Concurrency 1: 37.9 tps Concurrency 4: 82.8 tps Impressive progress in the Rapid-MLX runtime. xitter.cf/TeksEdge/status/211491…
Same Mac. Same Qwen3.8-27B 4-bit weights but now a new Apple Silicon inference runtime gives us 🐌 oMLX → 25.3 tps 🐌 LM Studio → 26.0 tps 🚀 Rapid-MLX → 37.9 tps 👈 👀 That's ~46% higher decode than LM Studio in Rapid-MLX's own M5 Max 36GB benchmark. And Rapid-MLX is an Apache-2.0 MLX inference server built to run coding agents locally on Macs, with various harnesses 💻 Codex 🤖 Claude Code 🧑‍💻 OpenCode ⚙️ Pi 🔧 Hermes 💥 Crush 🪿 Goose It also reports Qwen3.8-27B throughput with 4 streams LM Studio → 69.7 tps oMLX → 75.3 tps Rapid-MLX → 82.8 tps These are Rapid-MLX's own benchmarks, one run per engine, and the serving configs differ. Rapid uses MTP, oMLX uses SSD cache, and LM Studio has its own configured context/slots. Rapid-MLX on GitHub link in ALT
1
3
416
Fibo 2.0 Fibo 2.0 Dev has a pretty interesting architecture for an 8B image model. It uses flow matching with a 44 block single stream DiT operating in the latent space of the FLUX.2 VAE. Qwen3 VL 4B handles prompt encoding, while a Perceiver resampler compresses the output into 256 to 512 tokens. Both image generation and editing share the same weights. VGL converts natural language into structured JSON, making individual scene attributes easier to control without changing unrelated details. The Dev checkpoint uses classifier free guidance, with 50 inference steps and a guidance scale of 5.0 in the official examples. Edit Turbo is a distilled variant designed for faster editing. Bria reports first place for image editing and second place for image generation among open weight models on Artificial Analysis. The combination of structured control, unified editing, and LoRA support makes this more interesting than another image generator focused purely on visual quality. Dev Link huggingface.co/briaai/Fibo-2… Turbo Link huggingface.co/briaai/Fibo-2…
80
I've used both GrokBot and Dots. Since their pros and cons are already widely documented, I'll skip that part. One critical caveat, though: They do not guarantee data persistence within their built-in VMs. Always back up your files to external storage like Google Drive to save your sanity.
56