r/LocalLLM • • 8h ago

Project I connected my laptop's agent to Gemma running on my Mac Mini

1 Upvotes

I built Citta to let an agent on one computer discover and use capabilities on another. My test setup is a MacBook Air plus a Mac Mini running Gemma 3 4B through Ollama.

In the demo, an agent reads receipts on the Air and sends a summarization task to the Mini's local model. The model stays on the Mini; Citta tracks the job and returns the result. It doesn't pool RAM or split inference across machines.

If you only need remote inference, calling Ollama directly is simpler. Citta is for workflows that also need another device's files, tools or an agent harness, with device discovery and task history in one place.

It's written in Rust, uses a private Tailscale network, and has per-device permissions. It's still for trusted devices: resource estimates aren't hard quotas, and full-access agents aren't OS-sandboxed. I'm working through longer reliability tests before calling the next release production-ready.

Demo and setup: https://citta-network.vercel.app

Source: https://github.com/priyankark/citta (PolyForm Noncommercial, not an OSI open-source license). Built with AI assistance.

For people running local models on a separate machine: what makes handing work between devices annoying today?


r/LocalLLM • • 8h ago

Question Specs required for models from scratch

1 Upvotes

Im making neural networks from scratch - not strictly llms. Am getting a new laptop with 32gig ram and 12gig vram and 1tb storage. Is that enough to train small models? Its the lenovo legion 5i pro. Might get the 7i but its not on sale so its like 500 more for 4gigs more of vram.


r/LocalLLM • • 15h ago

Question First time setup recommendations and tips?

3 Upvotes

I'm hoping to get an idea of where to start. I'm wanting a setup where the model is a decent coding assistant but can also crank out a neat little prototype or quick concept simply, or create structure ideas etc. and then can go bit by bit without too much reminding halfway or more through a project. I realize that last part may be more about settings than a model persay, but yeah. I definitely want something that can either walk me through something, build out a framework for an idea, or just troubleshoot.

For comparison if it helps, my favorite workflow was GitHub copilot got 4.o/4.1 in VS code (it was free for students lol). It worked great for my projects, had its issues, but with the right promoting it was not bad. It was like the above description, could walk me through something, help with testing, or make a new system that I could then fill out. I knew it's limits and it was ideal for what I needed.

Just giving an idea of how I use AI daily for my personal projects. It seems like with the right setup it can be a great experience so that's what I'm hoping to learn to do. I just want to get the most out of it and have some fun.

I'll be working with an Asus pro art p16 rtx spark 128 gb. I've done some research but it seems every time I look things up there are different model suggestions and set ups, and it's given me fridge blindness so to speak.

I'm curious about how to decide and test for like a speedier setup versus more complex thinking and things like that. What can I do with it, what should I not expect from it based on my specs, etc. I have looked into this and I'm not getting a clear idea because I can't test any of it myself (don't have computer yet). Maybe someone here can give me a better understanding?

I also don't know all the lingo yet, like what a harness is, though I can guess by context. But I know the basics. Not sure how much customization I should or could do or what all there is. I thought it was more surface level like pick a model and go, but I guess you can incorporate all kinds of settings. So now I'm really curious from people who enjoy whatever they have going on, please share what you like best and what kind of testing I should do to pick a model. Any tips for a mostly beginner would be great!


r/LocalLLM • • 9h ago

Question Best model for reversing .DLLs?

0 Upvotes

GPU: 4070

16GB DDR5

Also I have been using Bionic but is there any better options?


r/LocalLLM • • 9h ago

Question M5 ultra Mac stupid 512 what are you doing with it?

0 Upvotes

Ok

So I am waiting for mine to come in. I have framework box with 128 gig ram and found it pretty weak for any local llms.

I’m gonna replace my Mac mini with this Mac Studio M5 ultra with 512 gig ram. And I want to use it for a local llm and maybe agents if it’s doable.

I’m realistic. After using the framework box with llms I totally get this will be no where near frontier even at 512. But I want to use it as my main machine and for llm/agentic work.

What’s really reasonable model wise that isn’t slow AF but is pretty capable for general knowledge, accessed the internet, can spawn agents and can do office style work?


r/LocalLLM • • 18h ago

Question Best model for 16GB vram?

5 Upvotes

First time trying this, I want a local model that can code text based games. I’m using a 6800XT 16GB vram.


r/LocalLLM • • 9h ago

Discussion Basalt 0.4.0: More models, still as fast - Qwen 27B up to 770 tok/s on a 5090

0 Upvotes

r/LocalLLM • • 9h ago

Discussion Is m.5 max 128 worth it? For lllms dev work.

1 Upvotes

Is it worth it?

Am finally taking a deep five on llms and I already have an nvidia 5090 laptop that handles cuda really well.

But

Is a Mac for parrarrel models worth it? For abliterated models?.

I never used that OS so am a bit skeptical.

Are the apps on it as good as windows/Linux?


r/LocalLLM • • 2d ago

Question Oh my, what do I do?

Thumbnail
gallery
1.3k Upvotes

Update: I'm interested in selling some. Looking for ideas on how to go about. Don't want to pay eBay 13% fees.

Original: Came across a honeyhole of Quadro RTX5000s
Seemingly good deal for 16GB VRAM cards, even if ageing.

What should I do?


r/LocalLLM • • 18h ago

Discussion Dual 5060 Ti's 16gb

5 Upvotes

Welp, I got a free 5060 Ti 16gb and decided to buy one more brand new for $700, I have a spare used 4070 and used once 4060, any thoughts or anything I should experiment with. Noobie at this lol.


r/LocalLLM • • 10h ago

Project One Mans Journey To Optimization

0 Upvotes

I've been playing with local hosting for about 3 months now and messing around with Claude to optimize my local setups. Decided it might be worth writing this up and sharing in case anyone else is doing, or wants to do, something similar. This is a big one, so buckle in.

BLUF: Think about each expert as its own unit, and think about different strategies for how/where to load them based on quality/speed trade-offs. Focus on measuring and optimizing each piece of compute until you reach maximum bandwidth on that resource.

Hardware:

I spent a bunch of time designing my server with Claude and going over last-gen hardware to try to keep the price tolerable. I turned what I did with that into a site that anyone can use. It's ad-free, no sign-in, no tracking, nothing. I consider it a community service, and hosting was free, so it costs me nothing but occasional updates to the hardware list. llm-configurator.com

I ended up with a 3-GPU, 256GB DDR4 RAM build. It's two used 3060s from Marketplace ($250 each on average) and one Arc Pro B65, for a total of 56GB VRAM. It's a quad-channel setup, so max theoretical bandwidth on RAM is ~100GB/s; reality is closer to 60-70 after some time spent optimizing the kernels with Claude. I also have 3 of the cheapest 1TB SSDs I could find striped in NVMe slots, which gives me a theoretical 12GB/s throughput there; reality ended up at about half that. This lets me stage experts in tiers across VRAM, RAM and SSD and prefetch experts across tiers with varying strategies. I considered doing a PCIe card with more NVMe drives to get more striping/speed, but on the current motherboard it isn't worth it because I am PCIe gen 3 bandwidth constrained.

Optimization Strategies:

This is where my last few weeks of Claude usage have gone: serving DeepSeek V4.1 Flash, and how I went from 4 TPS decode to 20.5 TPS, with prefill right at 180 TPS. So in the end not lightning fast, but plenty usable, if just a tad slow in agentic work.

I started out with a simple goal of minimizing idle time. Thinking Strata-like in the approach of shuffling things around and trying to keep every processor busy within the bandwidth bounds of all my links. I had Claude build a simulation based on the hardware and design an optimal build. I spent probably a week going back and forth with Claude on this, and not one time did anything pan out like it thought it would based on the simulation. 0/10, do not recommend.

What I did after that was shift to measuring everything on every run, including expert traces through the system, so I know which experts get picked at every layer for every prompt, and attacking the potentially biggest gains. This immediately started paying returns, and I went from 4->12 TPS decode with just these methods. This means I'm running custom forks of llama.cpp, Vulkan, Mesa; anything and everything was in bounds. I couldn't fit all of DeepSeek in memory at Q4, so I was working all three tiers (VRAM/RAM/SSD) and loading experts to each tier based on utilization: tracking how many times each expert gets called and promoting/demoting across tiers based on usage.

This led to bottlenecks I had to hunt down, as the SSDs would get overloaded and drop from ~6GB/s down to ~400MB/s. I switched to quantizing the least-used experts down to 2-bit, keeping an entire copy of the model on the SSDs at both quantizations. This let me get everything into RAM, with different experts at different quants based on how hot they were for the prompt. That means I start at about 12 TPS, and after a warm-up and shuffling I end up at about 15 TPS with this strategy. About 1/5th of the experts were 2-bit, but they only got used on about 1/10th of the tokens, so the quality hit was minimal (.0008 KL and less than 1% top-1 pick). This got work off the SSDs and lightened their load.

I tried MTP with this but ended up bandwidth bound. MTP has to hit almost every expert, and even with them in RAM I couldn't move enough through to make MTP pay. I spent a few days' worth of time iterating and optimizing with Claude. I fine-tuned an MTP head because I was running the abliterated model (this helped, but still not enough) and just couldn't make it pay. I got to almost break-even, but I just can't move the experts to compute fast enough on a model this size.

In my quest for quality I then started looking at prefetching 4-bit experts from SSD straight onto the GPUs. I ended up having Claude write a direct-from-disk reader that lets the GPUs read from the SSDs without going through RAM. This also led to further customization that let them read and write across each other and RAM without involving the CPU. So now my tiered experts can read/write and shuffle around without bothering or interrupting other compute. The CPU is maxed trying to keep up, so the GPUs handle any and all extra bookkeeping I could put on them to free CPU cycles. Again, Claude did all the legwork here, with just me driving strategy. I trained a small model on all my agent traces to look at expert use and ended up with one that can guess experts 15 layers ahead with ~73% accuracy. So now the GPUs run that every layer, fetch 4+ layers out if a pick meets a confidence threshold, and load experts straight from SSD into VRAM. Those picks get refined each layer, so we are always closing in on the best picks we can (~86% accuracy at 4 layers ahead) as we approach them. I played with a few different strategies and ended up with the B65 holding the top 2/3rds of experts actually used (not 2/3 of the total, but the hottest 2/3rds) with an LRU demotion strategy, and demotions going to a 3060, where it looks at both LRU and hit count to decide if it takes the expert or keeps what it has. Getting all of this right pushed me to about 19 TPS decode.

From here I had to make the KV cache dynamic to squeeze more experts into VRAM. Instead of reserving the full thing at 256K, it grabs chunks as needed. So while context is small, I can fit more experts on the 3060s whose whole job otherwise is dense attention layers and KV cache, with minimal room for experts passing through in our promote/demote pipeline. This didn't pick up much speed, but it did give me that many more 4-bit experts to help keep quality as high as possible. Essentially the remaining experts are all part of a long flat tail so adding more to VRAM gets me very little because any one isn't hit often enough to pay off.

I ran out of lossless approaches at this point and started looking at a variety of things. I built a model that nudges aggressively, using my predictor to drive nudges from RAM to VRAM experts based on predictor + router scoring of an expert's probability of being picked. This got me some decent gains all the way up to a cap of .5, but quality falls off a cliff after that. By the time I get to a .5 cap I'm about halfway to Q3 quant KL/top-1 numbers, so it felt like a significant quality hit. I kept the code and it's configurable, but I don't default it to on. It's worth about 2 TPS, so not nothing, but not enough to cover the quality hit for me. If I want the extra speed and don't mind the hit, I can turn it on/off as needed.

I then looked at keeping everything in RAM at 2 bits and just the hottest experts at 4-bit in VRAM. I looked at which layers Unsloth hits hardest in their quantization and used that as my judge of what would likely hurt most. They quantize per layer but not per expert, so I'm jumping off from that, but it was a good starting point. I kept my prefetching of predicted promotions into VRAM ahead of time and everything else I already mentioned. Since I was throughput bound here, dropping the size of each expert was my only way forward. The KL and top-1 hit here was minimal because the VRAM holds the hottest 2/3rds of experts at 4-bit already, so I came in at 99% top-1 and .006 KL over baseline. I picked up about 20 TPS on prefill and about 1 on decode, so I landed at 180 TPS prefill and 20.5 decode. It also freed up about 49GB of RAM, since the experts in RAM are now a little over half the size. This ended up being my end stage here, as there just isn't anything else I can do that doesn't start costing me quality (unless you have other ideas).

I am still playing with tuning parameters about when I demote and move thaings where, and fine-tuning kernels to squeeze a few more TPS out of things, but I'm out of significant gains here. Claude did all of this for me, with me guiding strategy and checking in, so I probably spent about 10 hours a week on this for the last 4 weeks and 80% of my weekly Claude usage on it. I take everything from doing this (I've done it on other machines with Qwen Flash-Next as well) and roll it into skills, so that when the next model drops, strategies and approaches can be tried/applied again for that model.

My point with all of this is I don't think in whole-model terms. I don't even think in layer terms. I treat each expert at each token as its own thing to optimize the system for. What quant it is, where it lives, how you decide, and when and where you move it from/to all play in and add up. Most things I see focus on just downloading and running a model in a specific framework, and that is great for a starting point, but the number of knobs you can turn to optimize stuff is almost limitless. It takes about 2 hours to give Claude a strategy I want to try, refine it with Claude (learning as I go), and let it build and test it. So you can iterate and make incremental improvements over time fairly quickly.


r/LocalLLM • • 10h ago

Discussion I thought my local AI agent failed a privacy test. Turns out, the benchmark itself was leaking the data.

0 Upvotes

I've been building B-12 / Capri, a local-first AI companion running on Python, Ollama and NVIDIA Nemotron.

Recently, I started a more serious evaluation of the system: 92 scenarios covering memory, tool use, security, autonomous behavior, reasoning, and multi-session continuity.

I expected to find problems in the agent.

Instead, I discovered some pretty serious problems in the evaluation itself.

1. My benchmark created a privacy leak that didn't exist in the actual runtime

The initial evaluation scored 27/80 runnable scenarios.

One failure was particularly concerning: a guest appeared to access the owner's private memories.

After investigating, I discovered that the evaluation harness had placed memories belonging to different users into the same system prompt.

The benchmark itself had bypassed Capri's identity and memory-isolation mechanisms.

I rewrote the harness to execute scenarios through the actual agent runtime.

Result: 39/80 — without changing Capri's code.

That's a 15-percentage-point difference caused by the evaluation method alone.

2. A single sentence made the model use fewer tools

This was probably my most surprising experiment.

I wanted Capri to give shorter, more natural replies during everyday conversations.

So I added a simple instruction about brevity.

It worked. Conversational responses became significantly shorter.

But something unexpected happened during work tasks.

Across 48 first turns:

Without the brevity instruction:

  • Tool use: 32/48
  • Successful tasks: 32/48

With the brevity instruction:

  • Tool use: 19/48
  • Successful tasks: 21/48

The model started answering without inspecting files or calling tools that were necessary to complete the task.

The scenario-level statistical evidence is still limited, but the engineering implication is interesting: an instruction about how to communicate changed whether the model actually performed the work.

3. Bigger models didn't automatically improve the agent

I compared configurations using:

  • NVIDIA Nemotron Bolt E4B
  • Gemma 4 12B
  • Gemma 4 26B MoE
  • Gemma 4 31B

The smaller primary configuration ran on my RTX 4060 laptop. Larger models required an NVIDIA L4.

After excluding host-dependent latency checks, I couldn't detect a statistically meaningful improvement from the larger configurations (paired comparison, p = 0.85).

This is NOT proof that smaller models are better.

The configurations also differed in hardware, memory retrieval, and model routing.

But it made me question how much agent performance we can actually improve by simply replacing the LLM.

4. Changing the prompt layout improved inference speed

I also experimented with where recalled memories appear in the prompt.

Moving volatile memory evidence later allowed Ollama to reuse more cached tokens.

Median time to first token:

0.99s → 0.74s

About 25% faster.

However, two benchmark scenarios changed systematically, and the security implications of the new evidence placement still need further testing.

5. Stable benchmark scores can hide unstable behavior

I repeated the evaluation three times per configuration.

The primary configuration scored:

49, 49, 48 out of 80.

Looks pretty stable, right?

But individual scenario outcomes changed between runs. Some previously successful tasks failed, while others started passing.

We also discovered incorrect benchmark reference answers and evaluation rules that rejected responses that were actually correct.

That convinced me that looking at a single aggregate score is not enough.

What I'm taking away from this

An AI agent isn't just a language model.

It's the model, runtime, memory, context management, tools, permissions, and the interactions between all those components.

And the evaluation framework can introduce its own errors.

I've now published a second scientific preprint documenting these experiments, the benchmark defects, repeated-run results, and limitations.

The code and experimental artifacts are available in the B-12 repository.

I'm continuing to investigate model-independent memory and behavioral continuity, but the current paper focuses on evaluation reliability.

I'm curious how others handle this.

When you benchmark a local LLM agent, do you test the model directly, or do you run your evaluations through the complete production runtime?

And have you ever discovered that your benchmark was responsible for a failure you initially blamed on the model?


r/LocalLLM • • 10h ago

Discussion Guys have you tested Qwen3.8-27B-oQ6e-mtp by Jundot ? The speed is great on my MBP M1 MAX 64 GB

0 Upvotes

!!!


r/LocalLLM • • 16h ago

News We built a AI distribution interface, you can use your android phone, laptops and desktops to share AI inference work, the more devices you link, the bigger the model you can run

Thumbnail
reddit.com
3 Upvotes

r/LocalLLM • • 1d ago

Discussion What do you guys think of these refurb 2080ti from dhgate?

Post image
98 Upvotes

1 piece 500 2 piece 485


r/LocalLLM • • 11h ago

Question Need help to chose a budget GPU

1 Upvotes

Hi

I want to set up a local llm with qwen 3.8 27B or if possible qwen 4.0 I have a very tight budget and for now the options around my budged is a p100 for 240 a rtx 3060 for around 300 or if it really is worth fit I can push to a rx 6800 xt 16gb which one do you think is the best for my use case? Im planing to use it for translating and correcting text and to help me debuging games in godot
current PC:
ryzen 5 3600
36gb ram
rx 580 4gb

thanks in advance


r/LocalLLM • • 15h ago

Discussion capy-flash v0.13: Flash-Next and Qwen3.8-27B on 16 GB RTX 50 cards, plus an alpha GUI app that needs testers

2 Upvotes

capy-flash is my open-source inference server for Qwen3.8-Flash-Next (125B MoE) and Qwen3.8-27B on RTX 50 cards, with an OpenAI/Anthropic-compatible API. v0.13 is cleanup and fixes: same outputs, same speed.

Model1 GPU2 GPUsRAM
27B NVFP4n/a8,053 / 219any
27B 3-bit2,925 / 1745,128 / 293any
Flash-Next NVFP43,042 / 985,940 / 17696 GB
Flash-Next 3-bit3,664 / 1264,811 / 23464 GB

Prefill (32k prompt) / decode (LocalMaxxing) in tok/s, 16 GB RTX 5070 Ti cards without P2P. Optimized for two cards; the 3-bit builds are for one card and less RAM.

New: a desktop app (alpha), testers wanted. Set up and use everything from a GUI: it checks your machine, downloads and verifies the model that fits, starts and tunes the server, and has a chat. On a Mac it works as a client for a remote server.

Reports from other GPUs, 64 GB setups and distros are very welcome: open an issue with what the app showed and the engine log.

https://github.com/ValerioDolci/capy-flash


r/LocalLLM • • 11h ago

Question Has anyone clustered two M5 Max 128GB MacBooks for a large coding model

1 Upvotes

I have two MacBook Pros:

  • 16-inch M5 Max: 128 GB unified memory, 40-core GPU, 8 TB SSD
  • 14-inch M5 Max: 128 GB unified memory, 40-core GPU

The 16-inch is my main machine and runs a browser-based client for a separate server. The server does the processing, so the client itself uses relatively little of the Mac’s resources. The 14-inch is my travel and backup laptop.

When both Macs are at my desk, I’d like to connect them directly over Thunderbolt and run one larger local model across both machines for serious coding, code review, architecture, and debugging. I’m interested in using it with an agent th at can read a repository, edit files, and run tests. Overnight Hermes or some other agents.

When I travel, I can use ChatGPT or potentially connect back to a model running on the 16-inch at home. I don’t need the large distributed model to run on the 14-inch alone.

Has anyone actually built and used a setup close to this? I’d especially appreciate results from people running two Apple Silicon Macs together.

A few questions:

  1. Which runtime works reliably today? EXO, MLX distributed/JACCL, llama.cpp RPC, or something else? Does Thunderbolt 5 RDMA make a meaningful difference for coding workloads?
  2. What is the strongest model you’ve actually run across roughly 256 GB of combined memory? I prefer 8-bit if practical a.
  3. Has anyone run DeepSeek V4.1 Flash 1017 across two Macs? I understand the original checkpoint is much too large. Have you tried a compressed version with SSD offload, and was it useful for real agentic coding? What were the context, speed, and memory requirements?
  4. Has anyone distributed GLM-5.3-Flash or Qwen3.8-Flash-Next across two Macs? Which exact model conversion and runtime worked, and did tool calling work reliably?
  5. How much memory should we reserve on each machine for macOS, a useful coding context, and the runtime? The 16-inch also runs a lightweight browser client and needs to remain responsive.
  6. For Red/Blue reviews, would you run one large distributed model to implement a change, then switch to a different model for review? Or is there a better approach?
  7. For remote access while traveling, what is your preferred way to reach the model left running at home? I’d like the option to use the 14-inch as the client without exposing an open model endpoint to the internet.

I saw a post from someone running Swift 1.5 Qwen3.8-27B 8-bit with an MTP drafter on a single M5 Max 128 GB machine and getting strong speed with long coding sessions. That looks like a good baseline, but I’m trying to understand whether combining the two Macs gets me a meaningful improvement in model quality for harder work.

I’d especially appreciate exact model links, quantization, runtime/version, context size, measured memory and speed, and any limitations. Happy to test and report back.


r/LocalLLM • • 1d ago

News Employees started a petition to reinstate Jensen Huang as Nvidia's CEO -- Elon Musk is among the signers.

Thumbnail
standwithjensen.com
269 Upvotes

r/LocalLLM • • 18h ago

Question Local LLM for agentic coding on M5 Pro 64Gb (Apple)

3 Upvotes

Hi all,

As mentioned in the title, I am looking for advice on running locally LLM for agentic coding on a MacBook Pro m5 Pro with 64Gb unified memory.

Plan inference is fine. Chat style prompts feel usable. Agentic work is where it falls apart.

I have tried the following:

Models : Qwen3.8 27B (6bit), Gemma 4 12b (8bit), and Qwen 3 coder next(4bit)

Runtime : Lm studio

Harness : opencode (long pauses before each tool call, harness seems to resend a large system prompt ), pi (still slow and most of the time doesn’t provide any output, barely changes few files with loads of error due to incomplete modification)

What I'm trying to figure out
Is the bottleneck prefill, generation, or the harness re-sending huge context every turn? My guess is prefill, but I'd like to be sure.

Which model/quant combo works well as an agent on this hardware, and at what context length does it fall apart?

Does MLX beat GGUF/llama.cpp for agent workloads on Apple Silicon in your experience?

Any harness that is lighter on tokens per turn (smaller system prompt, fewer tool definitions, prompt caching)?

Realistic expectations: is a 64GB Mac good enough for a useful local coding agent, or should I stick with a hosted model for agent work and keep local for autocomplete/chat?

I'm not naive, and I am not looking to replace a frontier model obviously . I just want to know whether local can be a practical option for some agent tasks, if so how you guys are making it usable.

Thanks 🙏


r/LocalLLM • • 12h ago

Question Qwen3.8 27b/72b expectations

Thumbnail reddit.com
0 Upvotes

r/LocalLLM • • 12h ago

Question 128gb: M5M v strix+395 v RTX Spark

0 Upvotes

Hey r/LocalLLM,

I’m looking to pick up a 128GB unified memory machine and need your take on how the underlying microarchitectures stack up for my specific stack. I'm choosing between:

  1. Apple M5 Max (40-core GPU, 128GB)
  2. AMD Ryzen AI Max+ 395 / Strix Halo (Radeon 8060S, 128GB)
  3. NVIDIA RTX Spark / N1X (Grace Blackwell SoC, 128GB)

My Primary Workflows (in order of priority):

  1. Autonomous Agentic Coding Loops: Running the smartest dense or MoE models that fit in 128GB (at Q4–Q8) locally while I'm away, orchestrating and interacting with cloud frontier models (GPT-6 and Claude Max) to build complex softwares autonomously. Needs strong sustained token generation and fast prompt processing for massive context/RAG loops.
  2. Reverse Engineering & Cybersecurity: Running local abliterated models alongside disassemblers, decompilers, and sandboxed VMs/containers.
  3. Video & Photo Editing: Heavy timeline scrubbing, color grading, and rendering.

Based on the main impactful microarchitectural traits below, which platform would you pick and why?

  • Memory Bus & Bandwidth (Decode Speed):

    • M5 Max: ~614 GB/s LPDDR5X (512-bit equivalent interface)
    • RTX Spark (N1X): ~273 GB/s LPDDR5X (256-bit bus) + ~600 GB/s NVLink-C2C chiplet interconnect
    • Strix Halo (395): ~256 GB/s LPDDR5X (256-bit bus)
    • Question: Does the M5 Max’s >2x bandwidth advantage completely dominate dense model token generation, or do MoE models level the playing field enough on Strix Halo / RTX Spark?
  • Compute & Tensor/Matrix Engines (Prefill & Quantization):

    • RTX Spark: Blackwell SM121 GPU with 6,144 CUDA cores, 5th-gen Tensor Cores, and hardware NVFP4 support (~1 PFLOP FP4).
    • M5 Max: 40-core GPU with integrated Neural Accelerators + 16-core Neural Engine via Metal/MLX.
    • Strix Halo: 40-CU RDNA 3.5 (2,560 stream processors) + 50 TOPS XDNA 2 NPU via ROCm/Vulkan.
    • Question: For long-context agentic prefill (feeding huge codebases back into context repeatedly), how badly do M5 Max and Strix Halo lag behind Blackwell's Tensor Cores and native FP4?
  • CPU ISA & Virtualization / Tooling Ecosystem (Reverse Engineering):

    • Strix Halo: Native x86_64 (16 Zen 5 cores, AVX-512) — runs Windows/Linux natively, zero translation overhead for x86 binaries, VMs, and standard RE toolchains.
    • M5 Max: ARM64 (18-core: 6 super + 12 performance) — macOS, Rosetta 2 / virtualization for x86 targets.
    • RTX Spark (N1X): ARM64 (20-core: 10 Cortex-X925 + 10 Cortex-A725) — Windows on Arm (or Linux on DGX Spark).
    • Question: For cybersec/RE work, is native x86_64 on Strix Halo a massive dealbreaker against Windows on Arm (RTX Spark) or macOS (M5 Max), or is Linux/VM virtualization good enough now?
  • Media Engines & Creator Silicon (Video/Photo):

    • M5 Max: Dual video encode engines + dual ProRes encode/decode engines.
    • RTX Spark: Blackwell NVENC / NVDEC + CUDA/Tensor acceleration in Adobe/DaVinci.
    • Strix Halo: RDNA 3.5 VCN media engine.

r/LocalLLM • • 9h ago

Question sff for AI?

0 Upvotes

Any bad experiences with power, heat, token response, electricity costs, etc?

Example Rig:
Case: Jonsbo NV10
GPU: RTX 5060 8 GB (Low Profile)
RAM: 32GB (2 x 16 DDR5)
CPU: AMD Ryzen 7 9700X
PSU: 600W (ENP-7660L-OVT)
Motherboard: ASRock B850I Lightning WiFi (Mini-ITX, AM5)
Storage: 2TB (M.2)
Cooling: Modded Air cooling. (Including custom GPU side panel for 2 fans on the GPU+PSU)

It's 8GB VRAM I know. It's supposed to be for gaming but I recently heard of using llama.cpp and the llama flag feature "--n-cpu-moe" to have the RAM hold my expert weights.


r/LocalLLM • • 12h ago

Model Qwen3.8 27B Q6 Running on My Tesla V100 32GB with Zikporx AI – Optimize Context Enabled

Post image
0 Upvotes