AI·Community discusses upgrades from Qwen3.6-27B, recommending options like DeepSeek V4 Flash or GLM-5.2 requiring 100-250GB VRAM for noticeable performance gains.
media · en · weight 0.9
r/LocalLLaMA
AI·Sources say China's DeepSeek is developing its own AI chip, potentially advancing domestic AI hardware capabilities amid global tensions.
AI·A user shares benchmarks of dual RTX 3090 and Titan RTX cards running llama.cpp with Qwen3.6-27B at 180k context, comparing tensor and pipeline parallel modes for PCIe transfer efficiency.
AI·llama.cpp build b9966 fixes regex recompilations for -sm tensor mode, caching patterns per tensor to reduce CPU overhead on decode threads.
AI·Questions costs and viability of aftermarket SXM2 boards for two V100 GPUs, comparing to consumer GPU setups.
AI·The post shares practical recipes and benchmarks for running LLMs on popular consumer hardware, with a new website listing hardware-filtered setups and user-voted usage stats.
AI·A $100 setup using three NVIDIA P102 cards delivers 20 GB VRAM and 448 GB/s memory bandwidth, sufficient for three concurrent LLM users with high context and better speeds than costlier lower-VRAM cards.
AI·User compares 5090 at 600W full compute and prompt processing vs shunt-modded 6000 PRO MaxQ water-cooled at 300-600W.
AI·The author benches a quad 5060Ti setup for Qwen3.6-27B code generation using MTP, reporting 608 tokens/s prefill and 52.2 tokens/s decode at 256k context on a cost-effective build.
AI·Discusses feasibility of running Qwen 122B on 64GB RAM + 24GB VRAM and suitable settings.
AI·Introduces Flaxeo Image, a local desktop UI for Stable Diffusion C++ that exposes model, hardware, and video options.
AI·User upgrading from dual RTX 3090 asks for advice on adding cards for 100-110 GB model support, weighing 2x modded 48 GB 4090, 2x A6000, or 2x 5090 in hybrid setup.
AI·Asks how far context window can be stretched with Qwen 3.6 27B at Q8_0 before reliability drops.
AI·Identifies dual 3060 MoE loading limit at 12 layers VRAM for Qwen3 35B/122B with CPU offload.
AI·Shares tool for tweaking models' J-Space using Anthropic Jacobian-Lens to create super harmful behavior.
AI·User with RTX 4090, 3090Ti, and 128GB RAM struggles to run larger models like 122B due to VRAM limits while Qwen3.6-27B runs efficiently without using system RAM.
AI·Follow-up post details data-engineering optimizations that scaled a SQLite/FTS5 patent database from 3.5M to 5.36M records while classifying them with Nemotron 9B on an RTX 5090.
AI·Questions why providers make high-parameter MoE models (e.g. 122B with 10B active) instead of simpler dense equivalents.
AI·Reports EPYC 9374F CCD benchmarks using ik_llama.cpp; finds limited decoding gains vs older 9135 at low thread counts.
Politico: Wall Street’s new obsession: Which CEOs have Trump’s ear?: https://www.politico.com/newsletters/politico-influence/2026/07/10/wall-streets-new-obsession-which-ceos-have-trumps-ear-00993324 submitted by /u/Nunki08 [link] [comments]
AI·Achieves 50-54 tok/s for Qwen3 30B A3B float8 on 16GB RTX 5060 Ti using custom CUDA/C++.
AI·Qwen3.6 35B-A3B Q8_0 model (no KV quant) generates full HTML flight simulator in single prompt and is praised as stronger than Q4_K_M on GPU due to better CPU performance.
I ran Grok Build CLI (v0.2.93) through mitmproxy. It uploads your entire repo as a git bundle (full history) to xAI's Google Cloud — independent of what you open. With the prompt literally "do not read or open any files," a file I planted came back verbatim when I git clone-d the captured upload. Separately, files it reads (incl. a .env with API_KEY/DB_PASSWORD) go to cli-chat-proxy.grok.com verb…
Hi everyone, A year ago I began pre-training language models exclusively on 1800’s London data. Recently I have completed my largest dataset ever, containing 40B tokens or 160GB of 1800-1875 english data from England and the United States. I will soon train a 2B parameter model on it, but for now I’ve trained a 500M parameter evaluation model on a 5B token sample. I have also fine tuned the eval …
Share what your favorite models are right now and why. Given the nature of the beast in evaluating VLMs (untrustworthiness of benchmarks, immature tooling, intrinsic stochasticity), please be as detailed as possible in describing your setup (at least hardware and inference engine) nature of your usage (what applications, how much, personal/professional use) tools/frameworks/prompts etc. Rules Onl…