Register and share your invite link to earn from video plays and referrals.

Wësche
@WescheNex1q
Day time artist and night time AI enthusiast. Building & benchmarking frontier LLMs on 4x DGX Spark clusters + Mac. Creator of Vesica Studio. Houston
731 Following    3.1K Followers
Qwen3.8-27B Mac m4 max vs DGX spark: same engine (TensorFold 0.6.5 + DFlash2), same seeds: DGX Spark • 4-bit: 82.9 · 52 min (~69 tok/s) Mac Studio M4 Max • 4-bit: 83.6 · 71 min (~50 tok/s) • 8-bit: 84.7 · 95 min (~38 tok/s) Hardware moved it <1 pt. 8-bit bought +1.1 for 2x the memory. Spark-Bench v7, 80 tests, 0 errors. bf16 lands tomorrow. Run your own benchmarks:
Show more
Frosty dropping the knowledge
Learning with Frosty: Lesson #1# I call it DWM-Domain Weight Modification really friendly with non-ablated models assist. Try it out and let me know. ❄️QWEN 2.5 DENSE ARC ONLY - DO NOT USE THIS ON M.O.E.❄️ it will BREAK the model. (Thats lesson #3#)
Show more
Running @ViC305's GLM-5.3 753b recipe on 4 Sparks took four fixes on our cluster: build the CUDA kernels before loading (warm-up OOM) one NFS copy of the 319GB pack hand-written hosts (cloned machine-ids) swap off Result: 84.4. All scripts are open: Credits: @ViC305 (quant + recipe), TensorFold, the DFlash2 drafter @Zai_org
Show more
GLM-5.3 753b went from 70.8 to 84.4 on Spark-Bench by changing the quant. @ViC305's SAGE MixedK 3.38bpw, 4x DGX Spark, TensorFold TP4 + DFlash2. Vs the 2.75bpw run: +13.6 points. 80 tests, 2 repeats, thinking off, uncapped. O errors. GLM-5.3 full scored 70.5 on our long-output builds, the best of any model we've tested. GLM-5.3-Flash got 42.1. Overall 84.4 on 4x DGX Spark Reliability (both repeats pass), Full vs Flash Code: 75.7 vs 90.0. Robustness: 75.0 vs 50.0. Long output: 89.2 vs 56.2. Agentic: 88.0 vs 83.3. Visual: 82.0 vs 84.2
Show more
🚀 FULL GLM-5.3. FOUR DGX SPARKS. A NEW PARETO-FRONTIER CONTENDER. This is a HUGE personal milestone for my SAGE work! 🔥 My GLM-5.3 SAGE EXL3 3.38 bpw brings the full model down to 319 GB while preserving ALL 19,200 routed experts. No pruning. No expert merging. Every bit matters. 🎯 INDEPENDENT-SET FIDELITY • KL divergence: 0.082388 nats • BF16 top-1 agreement: 91.1523% • 10,240 scored positions on text excluded from calibration ⚡ FOUR-SPARK PERFORMANCE Around 41 tok/s average (69 tok/s burst) across six real prompts with DFlash2, with drafted replies matching serial decoding token for token. 256K-context serving demonstrated. Sized toward a 1M-context memory target, with full-length inference validation still ahead. The goal is the highest-fidelity full GLM-5.3 possible on four Sparks WITHOUT sacrificing the memory needed for 256K–1M context. Not just making the weights fit, but leaving room to actually USE the model. 🙏 A MASSIVE thank you to @cfontes, who personally funded the compute required to make this model possible. This release would not have happened without his support! And we’re not done. He’ll be releasing a recipe soon that’s going to blow everyone’s minds! 🤯🔥 This is what community-backed local AI looks like. More capability, less memory, and people coming together to push what’s possible. 💪 Model 👇
Show more
GLM-5.3-Flash vs Qwen3.8 Flash-Next: Both on 2× DGX Spark, same 80-test Spark-Bench: -GLM 84.8 -Qwen 79.4 (vLLM) / 77.9 (TensorFold) GLM wins most categories. The biggest gap is long context. Where each one wins • Long context: 70.8 vs 21.6–27.9. GLM found the planted fact on the hard needle test, Qwen missed it on both engines. • Code: 90.2 vs 85.7–87.1 • Visual: 79.8 vs 71.4–75.0 • Tool use: 78.2 vs 58.2–75.6 • Agentic: 78.5 vs 67.1–75.1 Takeaway: Qwen follows instructions and formats more precisely. GLM is the stronger generalist: it codes, builds and retrieves better. Same 80 tests, uncapped, 2 repeats.
Show more
Got one DGX Spark? You can run a 2.49bpw GLM-5.3-Flash fine-tune that scored 85.1 on our full 80-test Spark-Bench. Clone, build, serve: Thanks @vic305 for the SAGE quant.
RED-SNOW-5.3-FLASH EXL3 is LIVE for both ONE and TWO DGX Sparks. 🥵❄️ ONE Spark: 2.49 bpw, 90.32% top-1, up to 61.7 tok/s TWO Sparks: 4.91 bpw, 96.85% top-1, KL 0.01174 New collab with @Blackfrost_AI. RED-SNOW is an abliteration of GLM-5.3-Flash with a cyber/security fine-tune, built for authorized red-team operations. I took the BF16 release and built two SAGE MixedK EXL3 targets depending on how much hardware you have. 𝗢𝗡𝗘 𝗗𝗚𝗫 𝗦𝗣𝗔𝗥𝗞 2.49 bpw Top-1 agreement vs BF16: 90.32% Mean KLD: 0.1190 Single-Spark decode: ExLlamaV3: 38.7 tok/s TensorFold: 41.0 tok/s REXL3, co-collab stealth engine with @mr_r0b0t : 61.7 tok/s 👀🤫 That is the pack for people trying to squeeze the entire model onto one Spark. 𝗧𝗪𝗢 𝗗𝗚𝗫 𝗦𝗣𝗔𝗥𝗞𝗦 4.91 bpw Top-1 agreement: 96.85% Mean KLD: 0.01174 That is 9,917 / 10,240 positions choosing the same next token as the BF16 reference runtime. This is the quality-first build. SAGE does not just flatten every expert to the same precision. It allocates bits across the model based on sensitivity, which is exactly why I wanted separate 1-Spark and 2-Spark releases instead of forcing one compromise pack on everyone. Both are standalone EXL3 checkpoints. Vision components are packaged. MTP is preserved. Authorized research/security use only. Huge thanks to @Blackfrost_AI for trusting me with another collaboration. And yes, that 61.7 tok/s REXL3 result is something I’ll talk a lot more about soon. 🥶 Each repo has a proper deploy.md file for proper deployment to your Spark setup! Actively working on the 2 spark deploy.md so its validation stage but it will be updated shortly after validation! The one spark deploy.md is already validated! ONE Spark: TWO Sparks: RED-SNOW-5.3-FLASH COLLECTION:
Show more
RED-SNOW 2.49bpw, 1 DGX Spark: 85.1 GLM-5.3-Flash 4bpw, 2 Sparks (TP2): 84.8 @ViC305 SAGE process shows in this test that almost 40% fewer bits can perform just as well or even better than a flat 4bpw quant. -Overall: 85.1 vs 84.8 -Long output: 61 vs 42 -Instructions: 97 vs 89 -Visual: 90 vs 80 -Tool use: 85 vs 78 Full Spark-Bench, 80 tests, thinking off, uncapped, zero errors. RED-SNOW is @Blackfrost_AI security fine-tune of GLM-5.3-Flash, so this is fine-tune + quant vs base + quant Engines differ (exllamav3 vs TensorFold)
Show more
Getting the itch to build something new so going to start a new clothing/shirts apparel brand, all hand drawn geometry i do, but using ai for the website/marketing. Calling it Vesica apparel
Le Chonk vs full GLM-5.3 on the same voxel pagoda prompt. -50K tokens vs 126K. 19.5 min vs 72. Both ran first try, untouched. Thinking on, temp 0.7, no output cap. GLM local on 4 Sparks, Mistral via @OpenRouterAI I think it did a pretty impressive job
Show more
My first PR into oMLX just got merged 🎉 Text cut through the middle of an emoji used to crash requests with a 500. Now they get a clean 400 that tells you which field is broken. Thanks @jundotkim
Show more
Same koi pond prompt, two GLMs on DGX Sparks: -GLM-5.3 Flash (2 Sparks) 90,852 tokens · 59 min · 26 tok/s Worked first try, no repairs -Full GLM-5.3 753B (4 Sparks) 136,640 tokens · 70 min · 32 tok/s Bigger world, but needed a 7-line fix to show its water Bigger model, more thinking, not automatically a better first draft.
Show more
Fully healed tattoo I did over a year ago, total of 3 sessions of 6-7 hours each
Could be cool but comparing it to glm 5.2, inkling and nemotron ultra don’t give me high expectations. Why not compare it to 5.3?
Introducing Beam: a highly efficient agentic open model with 501B total parameters and 23B active. - Frontier reasoning efficiency - Advances the Western open frontier on coding & agentic tasks - Trained end-to-end from scratch Full weights release this month. Learn more about Beam:
Show more
Full GLM-5.3 (753B) on 4× DGX Spark ran the Tower of Babel Bench: one brief, then 6 hours of active time with no human to answer questions. The task: build the Tower of Babel in Blender "in extreme, exquisite detail" and host a web app showing its progress. What it did on its own: -planned milestones with time boxes and kept a dated journal -wrote the whole scene as procedural Python: 2,378 objects, 340 unique meshes, 128k faces -rendered low-res drafts to check its work, then four 1920×1080 Cycles finals -built and hosted its own web app: renders, 3D viewer, history, plan, live stats It also realized it had no vision, so it wrote a tool that turns its renders into ASCII brightness maps to "see" them. @matdmiller bench isn't "can it write code." It tests: -endurance: working hours alone and pacing against a clock -time management: slow renders in the background, no waiting around -context management: 262K window, compaction, helper agents -3D/spatial reasoning, coding and the final quality Every call, token, tool use and cache hit is logged. The run: -6:00 active hours, 0 crashes, 0 errors -274 model calls -178,868 tokens generated (97,653 reasoning) -10.36M prompt tokens, 92.3% served from cache -4 finals, 53–168 s each on CPU GLM-5.3 EXL3 2.75bpw · TensorFold TP4 (@u1tra_instinct image) · 262K context
Show more
More GLM 753B testing on 4 DGX Sparks Four people chatting at once: Full GLM-5.3, TensorFold TP4: -4 streams × 3,000 tokens, thinking on 12,000 tokens in 194.6 s 61.7 tok/s aggregate · ~16 tok/s each First token in under 1 s for all four. His 118 tok/s is real: we reproduced it with his benchmark (113–136 greedy). We just tested a heavier workload: 4 different prompts, sampled, 3K-token thinking-on replies. 1 stream: ~35–43 tok/s Setup: @u1tra_instinct 2026-10-04-opt image, TensorFold TP4, 32K context per stream, built-in MTP drafts (no DFlash2), temp 0.7, seeds 1–4, max_tokens 3000. Recorded live in Chrome. His published 118.5 tok/s is greedy, 256-token replies with a different script; his sampled 4-stream run is 69–71.
Show more
Reproduced @u1tra_instinct new full GLM-5.3 TP4 image with Tensorfold on our own 4× DGX Spark Two runs: prose: 40.7 / 43.4 tok/s (his 41.8) code: 36.6 / 40.6 tok/s (his 38.1) 25K-token prefill + needle: 22.7–24.0 s (his ~25 s), PASS clocks 2.4–2.5 GHz, 68–71 °C, 0 swap Long reasoning: 27.1 → 35.4 tok/s vs the previous image.
Show more
These are the number for TP=4 DGX sparks for Full GLM 5.3 that you can't fuck with... LFG!!! go get it!!!!
GLM 753B vs Flash, same voxel pagoda prompt, both EXL3 on TensorFold, all local -GLM-5.3 full (4× DGX Spark): 125.6K tokens, 72 min, ran first try -GLM-5.3 Flash (2× DGX Spark): 103.4K tokens, 58 min, 1 fix Same speed, about 30 tok/s. The big one got it right first time; Flash brought the color. Setup: full GLM-5.3 = @u1tra_instinct ' EXL3 2.75bpw + TensorFold TP4 recipe. Flash = @MiaAI_lab EXL3 TR3-4bpw. Both on TensorFold by @ashxhart Flash's fix: the scene called 4× but never defined it; I added the one-line fill loop in a copy, original kept. Recorded live in Chrome, no other edits.
Show more
GLM 5.3-753B vs Qwen3.8-27B Same Eiffel Tower prompt, both local -GLM-5.3 full (4× DGX Spark): 120.9K tokens -Qwen3.8-27B BF16 (Mac Studio): 78.5K tokens The 28× bigger model thought 54% longer and still finished in half the time. Look at the towers. Setup: GLM-5.3 = @u1tra_instinct EXL3 2.75bpw + TensorFold TP4 recipe on 4× DGX Spark (MTP drafts, 262K context). Qwen3.8-27B = official BF16 via MLX. Temp 0.7, thinking at max, no output cap. Both MP4s checked: 1200 frames, 20.000 s, 1080p60. Fixes logged in REPAIRS.diff; I can share the method and scripts.
Show more
🚨 Opus 5.5: Today vs. At Launch — Nerfed? 👀 With everyone talking about a possible nerf, I had to test it myself! I reran the Eiffel Tower benchmark, and honestly, I prefer the launch result. It honestly feels like Opus 5.5 got little nerfed. The tower itself might have slightly better detail now, but the surrounding buildings, trees, river, and overall scene look noticeably worse to me. One run doesn’t prove a nerf, but this comparison surprised me. I want to see whether the same pattern shows up in the night train benchmark next! 🚂🌙 What do you think: nerf or normal variation? 🤔
Show more
GLM 5.3-flash vs Mimo v2.6 Round 2 of the local Eiffel Tower duel. GLM 5.3 Flash: 80K tokens in 61 min. It needed 3 one-line fixes to run, then delivered the best tower of the four: real cross-braced lattice and base arches. MiMo V2.6 Flash: fastest (62.7K tokens in 23 min) and clean code first try, but the low shot falls through the ground into a black silhouette.
Show more
Deepseek v4.1 vs Qwen-next Same Eiffel Tower prompt, two local models on 2 DGX Sparks, thinking on. DeepSeek V4.1 Flash wrote 114K tokens in 49 min and the code ran first try: real cross-braced lattice, the Seine bend, La Défense in the haze. Qwen3.8 Flash Next was faster (77K tokens in 21 min) but needed 3 code fixes to run, and the river never shows.
Show more
Deepseek v4.1 vs Qwen-next Same Eiffel Tower prompt, two local models on 2 DGX Sparks, thinking on. DeepSeek V4.1 Flash wrote 114K tokens in 49 min and the code ran first try: real cross-braced lattice, the Seine bend, La Défense in the haze. Qwen3.8 Flash Next was faster (77K tokens in 21 min) but needed 3 code fixes to run, and the river never shows.
Show more
🚨 Opus 5.5: Today vs. At Launch — Nerfed? 👀 With everyone talking about a possible nerf, I had to test it myself! I reran the Eiffel Tower benchmark, and honestly, I prefer the launch result. It honestly feels like Opus 5.5 got little nerfed. The tower itself might have slightly better detail now, but the surrounding buildings, trees, river, and overall scene look noticeably worse to me. One run doesn’t prove a nerf, but this comparison surprised me. I want to see whether the same pattern shows up in the night train benchmark next! 🚂🌙 What do you think: nerf or normal variation? 🤔
Show more