The Unified Memory pool is what will continue to be the “game changer” in systems architecture, especially outside of data centers.<p>The reality is even cutting edge games and consumer workloads don’t actually take full use of the PCIe bandwidth of the GPU or the bandwidth of its GDDR memory. Even local AI use cases don’t substantially or meaningfully benefit from faster memory, at least to average consumers.<p>A unified memory pool does two things:<p>1) Lets systems optimize utilization based on need, rather than be confined to specific pools<p>2) Reduce overall memory cost, by letting system builders purchase a single type of memory in bulk instead of having to figure out GDDR vs DDR memory placement (important for SFF/portable machines)<p>So at a time when memory is expensive, unified pools make more sense. Even when memory becomes cheap and plentiful again, it’s just practical at this point to allocate a larger overall pool instead of managing discrete sets.<p>The <i>one</i> big drawback is security. A shared memory pool means side-channel attacks against memory from the GPU or CPU could potentially compromise the other as well, meaning memory-safe designs are going to be critical to security going forward (which is good for Rust adherents, I figure).
> Lets systems optimize utilization based on need, rather than be confined to specific pools<p>The trouble with this is that the different types of memory have different characteristics. Latency for ordinary system memory is actually <i>better</i> than it is for GDDR, because GDDR is optimized for bandwidth. RTX 5090 has 1.8TB/s of memory bandwidth with a 512-bit memory bus. The same bus width for DDR5-9600 would have better latency but only a third of the bandwidth.<p>CPU workloads are generally bounded by latency and GPU workloads are generally bounded by bandwidth, which is why they use two different types.<p>> Reduce overall memory cost, by letting system builders purchase a single type of memory in bulk instead of having to figure out GDDR vs DDR memory placement (important for SFF/portable machines)<p>The trouble with <i>this</i> is cost. In principle you could get the same 1.8TB/s of memory bandwidth as the RTX 5090 has, with the better latency of DDR5, by using DDR5 with a 1536-bit bus. This is indeed with multi-socket servers do, two sockets with 768-bit in memory channels per socket, but now check how much those system boards cost.<p>But the remaining alternatives are both worse. If you use GDDR for the unified memory then GDDR costs more than DDR and you're going to have significantly worse latency for the CPU. If you use DDR without a 3-4 times wider bus than the already-wide GPU then the GPU gets starved for bandwidth.
These are all good points that I agree with but rather than seeing an intractable problem I predict we'll see the role that GDDR would otherwise fill in this scenario replaced by a small block of HBM on the APU die. I don't know if it will ultimately end up unified or not but either way I don't think memory segmentation is the core problem here. Simply not needing to send transfers across the narrow and slow PCIe bus would fix most of the practical problems (at least AFAIK but I'm not an expert).<p>Transitioning over to wild speculation here, I think that most likely this will be treated as part of an absurdly large L3 (ala 3D V-Cache) or as an additional L4. In either case I expect the latency and power tradeoffs introduced to be tolerated as "good enough" even for the highest end consumer gear. (Actually I wonder if some sort of special case cache would be feasible, with memory addresses flagged by the graphics driver and regular CPU related stuff skipping over it entirely. But by then we've squarely entered the territory of vaguely unhinged rambling on my part.)<p>Alternatively if the performance caveats are deemed to be important enough to justify the added complexity it wouldn't surprise me to see the HBM treated as an independent memory pool analogous to that of a dGPU. That wouldn't change the current status quo with respect to the GPU APIs but it would significantly ameliorate the memory bandwidth bottleneck for inference workloads and from a software perspective is a drop in replacement. You'd still write the code targeting the dGPU with explicit swapping to RAM but when run on an appropriate APU it would get a massive speedup for free instead of suddenly being starved for bandwidth while also performing unnecessary copy operations.
> The reality is even cutting edge games and consumer workloads don’t actually take full use of the PCIe bandwidth of the GPU or the bandwidth of its GDDR memory<p>Game dev here. For anyone reading this - it’s not because we’re lazy, it’s because _it’s really hard to do_.<p>One of the biggest differences between the current generation consoles and the current gen PCs is unified memory.
I live with a game dev myself, so <i>I get it</i>. Hell, it's hard even for PC developers who want to do things without leaning on abstraction layers or existing engines. Managing multiple discrete memory pools, asset swaps or calls between them, getting the respective subsystems to exchange data at <i>just</i> the right time so as not to impact other code and drag down performance - <i>it's fucking hard in general</i>.<p>A unified pool of memory suddenly makes that simultaneously easier, but also far more flexible, which frees up developer time and bandwidth to focus on other, more important tasks.
How much of that difficulty comes from the chosen game engine? I assume the engine is the primary factor in how resources are allocated.
Both lots and none at the same time. The engines definitely make decisions for you but with unreal (for example) you can modify the RDG any way you see fit.<p>The problem is that when you need something in gpu you have to go through RAM first (unless you have DMA which is a more recent addition). That doesn’t just add latency it also adds an extra step of cache invalidation, so you have to plan for that from the highest level of gameplay. If you need to prepare for a GPU memory miss _and_ a CPU memory miss as a worst case all the time, it’s very hard to make good use of the bandwidth in the best case
One related question that you need to follow that with is the associated costs of switching the whole studio to another engine that's technically better, or if proposing teach studio tailor-make their own engine the costs of that engineering, if presumably they have or learn the expertise to surpass whatever they're using currently.<p>I'm not a game developer, but it would also seem to be a link between resource usage by the engine, and whatever content the production side are making. For all the commentary about how brilliant the id software engines are, if you examine the levels you pass through they're also very efficient with what they demand out of the engine - it's like an orchestra playing well together, not one instrument that means you can do anything.
I think much of the difficulty is just that, for example, the 1.8 TB/s of an RTX 5090 is a lot of bandwidth for a game to use. That's over 50,000 4k textures per second at 32bpp.
That sounds like a lot, but: modern renderers do between 20 to 40 passes, many of them in screen space. And each screen space pass typically reads from at least two input images, sometimes 3 or 4 even with optimally packed inputs. At 60fps that can quickly get up to way over 2000 full screen buffer reads per second and more for less than optimal access patterns in some algorithms. That also doesn't account for texture access during shading passes, which are somewhat random memory accesses.
Very true, but I'll point out that even those 2000 full screen reads per second at 4k are only 4% of the 5090's bandwidth. Sacrificing some of that speed for a unified memory architecture seems like a good trade.<p>Plus, DLSS can greatly reduce the bandwidth requirements for 4K gaming.
What? It's incredibly easy to take full use of memory bandwidth. For example, put proper volumetric smoke/fire/explosion sim in your game. But game developers don't do that because they are lazy.
And conveniently, by making your machine non upgradeable, it allows the manufacturer to enforce market segmentation / charge a huge premium for small RAM upgrade (<i>a la</i> Apple)
It doesn't -have- to be that way necessarily...<p>LPCAMM2/SOCAMM2 exist, heck I think Framework is using LPCAMM2 in one of their new laptops.<p>Heck, I'm willing to bet that a lot of manufacturers would rather go that route than soldered in, if for no other reason than the relative cost of warranty work between the two.<p>However, people probably need to stop being obsessed with ultrathin laptops for that to happen.
> However, people probably need to stop being obsessed with ultrathin laptops for that to happen.<p>I've never been able to understand this. Once we made it down to ~20 mm (which for the record still accommodates dual-stacked SO-DIMMs, a 2.5 inch bay, and a user replaceable battery but not an RJ45 jack) I don't understand what the practical impact of any further reduction is supposed to be. Regardless of how thin you make it the thing will still be a massive rectangle that you can't flex or press on.
> Regardless of how thin you make it the thing will still be a massive rectangle that you can't flex or press on.<p>There's <i>very</i> wide variation between laptops in how noticeably they'll flex or yield or creak when pressed. Laptops with a build quality that actually feels solid are far from being ubiquitous or even a majority.<p>Doubling the thickness of my MacBook Air would probably make it regress on that solid feeling, unless the weight was also significantly increased.<p>And regardless of whether current laptop form factors <i>could</i> accommodate a 2.5" drive, there's no use in doing so. That drive form factor is entirely obsolete for laptops and is just a waste of space and materials, and has been for about a decade.
I came here to say just this myself! Modern DIMM formats make SFF/portable builds with unified memory pools far more plausible than prior designs. There's absolutely no reason desktop machines couldn't implement similar DIMM formats or design a new board standard around something similar.<p>Unified memory doesn't <i>have</i> to be soldered on or serviceable. That's a choice Apple made because it fit their product vision, but it's not mandatory in the slightest.
Sir! I am typing this on a Lenovo Carbon X1, with soldered on ram, and you are EXACTLY CORRECT!<p>I would much prefer two SODIMM sockets with the option to go to 32MB shared video memory, or DDR4/DDR5. Give me OPTIONS!
Maybe I won't care about upgradeability <i>right now</i>. The architecture is clearly in flux, the roles of traditional "CPU" and "GPU" are rapidly evolving. Maybe in 5 years, or even 3 years, a brand-new machine from 2026 won't be worth upgrading for a new role due to a seriously different architecture, but would only be relegated to do something "traditional".
There is LPCAMM2, if manufacturers want to use it.<p>So, it does not have to be soldered.
LPCAMM2 is available in real systems at 7467MT/s and 120ns latency, vs apple (and intel) at 9600MT/s (and apple soldered memory at 100ns latency).<p>I don't know how linear or sensitive CPU and GPU benchmarks are to such a 20% slowdown, but i don't think Apple wants to pay it. And it looks like the next generation will be even closer to the SOC.
Until LPCAMM2 came along, using low power LPDDR RAM meant soldiering RAM to the motherboard.<p>If you wanted to get sleep right and improve battery life, that was the trade off.
I wish manufacturers could consider a hybrid approach. There should be no reason an architecture can't support both unified memory (effectively L4(?) cache), and cheaper, upgradeable system memory on sticks for old-school application use.
how about the LPCAMM route? Framework uses LPCAMM2 in 13 Pro laptop mainboards and claims that it satisfies the iGPU and NPU hardware without needing soldered RAM
Is that required or just a choice Apple made?
What do you mean by required? Apple's prices are notoriously disconnected from the cost of manufacturing.
I mean is it possible to make unified memory systems with good performance or is it not really feasible due to memory timing/trace length issues?<p>It’s possible if you’re willing to go with much slower RAM than GPUs like but CPUs often use. Thats what integrated graphics laptops have done for a long time right?<p>But can you get high end CPU and GPU performance with unified memory <i>and maintain user upgradable memory</i> in a reasonable way? Thats what I don’t know.
> I mean is it possible to make unified memory systems with good performance or is it not really feasible due to memory timing/trace length issues?<p>LPCAMM and similar solutions exist, but have never been demonstrated running at speeds that match what the leading soldered memory systems are using; there's always been some speed penalty. I'm not sure we've ever seen a system demonstrated using LPCAMM or similar for a 512-bit bus to match Apple's Max tier SoCs, so it's somewhat of an open question whether those solutions can offer upgradability at the high end of the market for unified memory systems.
> LPCAMM and similar solutions exist, but have never been demonstrated running at speeds that match what the leading soldered memory systems are using; there's always been some speed penalty.<p>LPCAMM2 supports up to 9600MT/s, which appears to be the same speed Apple is using.<p>> I'm not sure we've ever seen a system demonstrated using LPCAMM or similar for a 512-bit bus<p>Servers commonly use a 768-bit DDR5 memory bus per socket even without LPCAMM and LPCAMM allows shorter traces than traditional DIMMs. It's basically down to most existing DDR5 system boards/sockets having been designed before anyone was trying to run LLMs on consumer hardware, e.g. AM5 has a 128-bit memory bus and you're not changing that without a new socket. But every memory generation gets a new socket anyway, and the existing Threadripper Pro socket has a 512-bit memory bus as well.<p>Moreover, making the bus wider is "easy" -- the main problem with it is that it adds cost. Apple's least expensive machines use the same 128-bit memory bus as most PCs and the ones with the 512-bit bus cost as much as Threadripper if not more.
> LPCAMM2 supports up to 9600MT/s, which appears to be the same speed Apple is using.<p>The difference here is in what the standard defines on paper vs what is actually shipping in products and readily available off the shelf. Who's selling a whole system with LPCAMM2 certified for 9600MT/s? Intel's current-gen Panther Lake top of the line laptop chips are rated for 9600MT/s when using soldered LPDDR5x but only 7467MT/s when using LPCAMM2, according to their current datasheet: <a href="https://www.intel.com/content/www/us/en/content-details/872188/intel-core-ultra-series-3-processor-datasheet-volume-1-of-2.html" rel="nofollow">https://www.intel.com/content/www/us/en/content-details/8721...</a><p>That puts the current Intel-with-LPCAMM2 supported memory speed at 1.5 years and counting lag behind Apple's shipping memory speeds. Intel's own shipping memory speed moved past 7467MT/s a few months earlier than even Apple's.<p>> Servers commonly use a 768-bit DDR5 memory bus per socket even without LPCAMM and LPCAMM allows shorter traces than traditional DIMMs.<p>> Moreover, making the bus wider is "easy"<p>Citations needed. Servers aren't anywhere close to 9600MT/s yet; Intel and AMD are at 6400MT/s. The trace length advantages offered by LPCAMM2 don't necessarily mean the traces for the sixth or eighth channel would be short enough for 9600MT/s (which again, is not yet available even in a 128-bit configuration in shipping hardware). Adding more channels to even a LPCAMM2 configuration means adding more trace length, because only two modules can actually be adjacent to the CPU socket. (Maybe you could get to 512-bit with modules on the front and back of the board while maintaining trace lengths short enough to reach meaningfully higher speeds than regular DDR5, but so far nobody is doing that or even talking about it.)
You mean Apple prices are notoriously over priced, over hyped, under powered, and<p>"Abdul Jabar, couldn't have made these prices, with a sky hook."
both. soldered ram is faster. also Apple don't want to offer upgradblity after purchase.
Don't I/you wish. The mechanical junction adds no delay, only manufacturing expense, and the delay of purchasing new systems to keep up with OS bloat.<p>Actually the opposite is true. Socketed RAM can be made to overclock and adjust timings, while soldered ram, no. Two Lenovo's one soldered ( Carbon X1 ), one T590, one slot: Crucial 16GB, 260-pin SODIMM, DDR4 PC4-19200. Exact same processor, the X1 is DDR3 soldered on 532.0 MHz PC3-1066. The T590, has DDR4, PC4-19200, 1200Mhz.<p>Both have a Core i7 8665U... and the T590 is <i>much</i> faster, with socketed ram.
Are there no PCIe standards that are sufficient to support both use cases?<p>What happened to PCIe 8 and CXL?
AFAIK PCIe6 just started getting implemented in hardware last year... PCIe7 Spec was just released last year too...<p>PCIe6 is a much larger change than 'just bump up the transfer rate', the encoding changed too (on top of the new code length, it's no longer NRZ,) so everyone needed to design and validate both the new encoding block, negotiation, etc etc.<p>That said, I'm guessing PCIe7 will be a 'smoother' transition from PCIE6, i.e. we <i>might</i> see 7.0 products in 2027. That will theoretically get you ~240GB/sec, on an x16 link, or hypothetically a little less than the hypothetical max of a current Strix Halo. (I'm guessing however, that PCIe protocol overhead will make the difference larger.)
Don't really buy the economic argument. For 99% pf all workloads you need at least an order of magnitude more system memory than gpu memory.<p>Most systems barely need more gpu memory than what is required for video, browsing etc.<p>Just because we found a new usecase doesn't flip that on its head.<p>Besides, I want to keep doing what I'm doing today. So if I need 128GB today and my local AI needs 128 GB then I'd need 256 GB to keep doing the same work.<p>The argument rather seems to be that we shouldn't use such expensive memory on the GPU. Which might be true if you only want to do inference on it.
>[..] take full use of the PCIe bandwidth of the GPU or the bandwidth of its GDDR memory.<p>I'm honestly a little confused by what you mean here. Why would we want to maximize those things? Games are about consistent output under the frame deadline, not full saturation of the hardware.<p>Why would anyone try to saturate a 5090 with their game? The addressable market is tiny and you'd have to hope their full spec runs as well as or better than your test rig or they'll still not hit framerate.
You could do some sort of adaptive quality where you spend time incrementally improving fidelity until your frame budget is up. In practice I think that might be trickier than it sounds, but I feel like theoretically there's something there that could get you the best graphics your rig can handle without dropping frames. I've been considering doing something like this when I've been building a game/engine lately.
There's only so high you can go because the game assets have a maximum quality. Maybe you'll be able to max out the 5090 but what about the next flagship GPU?<p>You're also likely not going to maximize all of bandwidth, compute, etc. because one of them will likely be your bottleneck. And it might be different depending on the GPU, too.
DRAM optimized for CPU usage looks very different from DRAM optimized for GPU usage. You are leaving a lot performance on the table when you have a unified memory architecture. It makes sense in some situations, but it is not a silver bullet.
And here I am with 128GB Strix Halo longingly eyeing the Blackwell cards that spit tokens 10-20x the speed.<p>The question is ultimate shape of knowledge compression and bandwidth optimization at which we arrive I suppose.
If you haven't already, check/increase the GPU memory carve-out on your UEFI.<p>More details: <a href="https://rocm.docs.amd.com/en/docs-7.2.0/how-to/system-optimization/strixhalo.html#memory-settings" rel="nofollow">https://rocm.docs.amd.com/en/docs-7.2.0/how-to/system-optimi...</a>
Memory safety is orthogonal to side-channels, and hardware-enforced isolation (e.g. IOMMU) is more powerful than compiler-enforced isolation (but both are good!)
That was the main reason for the big hype around Memristors 15 years ago. High density, high speed persistent memory to completely remove the need for hdd/ssds, potentially even removing the need for external memory altogether. So frustrating that it still seems like we're a long ways from that becoming reality. There's some renewed interest in Memristors as they can simulate neural network connections in models, so maybe the funding will return for it.
The one example of persistent memory that managed to reach the mass market was Intel Optane/3dXPoint (still popular today among people looking to save on RAM costs) and that used a kind of phase-change memory, which is but tangentially related to memristors. ReRAM is somewhat closer, but it's also been less successful so far.
What is the difference between unified memory and shared memory?<p>Shared memory existed since the first CPU with an embedded GPU came to market and you could set in BIOS how much memory goes to what component.<p>I do have an opinion about how unified memory could be different, but I want a proper explanation.
I'm not sure everyone uses the terms consistently, but the difference is that the old "shared" memory was reserving a section to act as VRAM under the control of the GPU, ignored by the OS. The CPU ran the same kind of code pretending there is a "bus transfer" between host memory and graphics memory.<p>In unified memory, all the memory is host memory and data can go from program to GPU with zero copy movements. The addresses of buffers can be shared via appropriate MMU translation support, so that the application and graphics subsystem are communicating effectively through the basic RAM cache coherency protocols over the same buffers.<p>Edit to add: Aside from the zero copy transfer potential, it also means dynamic allocation strategies can shift the balance between host and graphics allocations on the fly. Individual image and message buffers can be allocated on the fly instead of setting a static split between the two worlds.
You got it in one! That's exactly what makes unified memory superior for current use cases, and different from the shared memory woes of old.
Reserved sounds like it would have been a better term now that I'm reading this many years later.
That's my understanding, or, maybe a better word would be "guess". The CPU telling the GPU: this is your memory now.
To some degree this is how it already feels like to program basically anything with dma today. You map hardware into an iommu and stop touching it when the hardware is supposed to use it, and then you reclaim it afterwards. So the model from the os feels the same, the difference is that it's not copying the memory into some local memory to operate on it.
Shared memory of the past meant reserving a part of the memory for the GPU, which could then not be used or accessed by the CPU. If the CPU wanted to access something, it had to copy it from the GPU's section of the memory to its own. Unified memory means both just fully share the same memory.
For these in specific, they appear basically transparently to the GPU. There's a lot of software/firmware stuff for this, but also a different hardware architecture - while the RAM is on the CPU die, the nvlink-c2c gives it extremely low latency and 600GB/s bandwidth between the GPU and CPU.
Marketing, mostly? But perhaps also more flexibility with how much memory the GPU can directly access without reserving it.
No. Let’s define terms, as others have pointed out they’re not perfect.<p>Unified memory is what Apple is doing, other phones do, and many low end built in GPUs have done in PCs for ages. There is only one physical memory pool. Both the CPU and GPU can access it at full speed.<p>This means no copying between pools of memory. No speed penalty accessing the CPU memory from GPU or vice versa. If the GPU only needs 2 GB to draw the desktop it only uses 2 GB of the pool. Or it can use 45 GB if it needs it and the CPU doesn’t. But all memory has to be the same speed, and that ain’t cheap given how fast GPUs like things. I don’t know if expandable memory is possible, and they use the same bus do they compete for bandwidth. Seems <i>theoretically</i> easier to program for to me.<p>The opposite is what’s been common in graphics cards since the 2D era. CPU and GPU have their own memory and can talk over PCI/AGP/PCI-E. This is what I think they mean by shared memory, if it’s not what’s the point in touting unified?<p>In this model if the GPU uses 2 GB of its 12 GB total, the other 10 isn’t available to the OS at full speed and I’m not aware of any operating systems that would use it for programs/cache by default. If the GPU needs 45 GB… too bad. You have to page things in and out of GPU memory over the much slower system bus. Starting a game means loading assets into main memory then transferring them to the GPU (newer tech can accelerate this). But the CPU can have slower memory than the GPU saving money. Memory expansion on the CPU side easy. And the CPU saturating its memory bus has no effect on the speed of the GPU memory bus because it’s physically separate. More complicated memory model but it’s the one everyone uses used to.<p>Which is better is a matter of opinion and workload needs.
Yes, I know there is an actual difference vs. dedicated GPUs with their own VRAM. I say it's marketing because Apple popularized the unified memory term even though, as you said, it existed in iGPUs long before Apple Silicon and was called shared GPU memory.<p>> I don’t know if expandable memory is possible<p>It technically is. These new systems (mostly) get their high bandwidth by using more channels (wider bus) of normal RAM modules. A system that has LPCAMM2 sockets should allow using the same LPDDR5X memory but you'd need a socket per two channels. A typical PC only supports two channels so having four (two sockets) would double the bandwidth.
System RAM has much lower bandwidth and less predictable access. Notably, the transfer from system to GPU is very slow. About 30x slower. LLMs aren’t designed to queue or parallelise operations to account for this. They just become much slower.
> Even local AI use cases don’t substantially or meaningfully benefit from faster memory, at least to average consumers.<p>I'm not sure what you mean by this. Memory bandwidth is the main bottleneck for single-user decode. The bottleneck is actually more severe for end-user inference than cloud inference, because end users don't have the option to increase arithmetic intensity by computing tokens for multiple clients in the same pass.<p>One thing we've learned from Apple is the viability of spamming more LPDDR5X channels (up to 1024-bit total bus width on M3U) as a means of achieving high bandwidth while keeping the cost/capacity reasonable.
Isn't the big drawback not having a swappable GPU? Perhaps that's not as important anymore but I'm not sure we've confirmed the market demand for that.
The "one big drawback" is the lack of consumer upgrades, and the seemingly arbitrary prices charged by vendors for memory upgrades at time of system purchase. I'm not saying it has to be that way, but seems like it has been so far :-(
Yeah, no. GDDR is functionally very different than SDRAM.<p>GDDR tries to push out as much bandwidth as possible, because that really matters for (traditional) GPU workloads. A constant but insignificant (= correctable) error rate is considered completely fine for GDDR, because that sacrifice allows the memory to be pushed much farther.<p>Meanwhile most (traditional) SDRAM workloads don't give a hoot about bandwidth but really care about latency. And ideally you want no errors, hence ECC RAM being so venerated.<p>If you unify memory, you're gonna have to choose to sacrifice one of those workloads or go suboptimal for both.<p>Weirdly enough this mostly matters for non-gaming workloads. The Apple M-series are absolute monsters in gaming, completely crushing the RTX XX90 editions in performance-per-watt, but as soon as memory bandwidth becomes paramount the M-series falls heavily behind.
Unified memory is only a feature because NVidia so aggressively uses VRAM for market segmentation.<p>The 5090 ($2k MSRP but realistically $3-3.5k) is almost the same as the RTX 6000 Pro (~$10k). Same memory bandwidth (1800GB/s). Slightly different CUDA cores (21k vs 24k). Big difference? VRAM (32GB vs 96GB).<p>NVidia ultimately doesn't want to upset this segmentation so the RTX Spark will never undermine their other offerings. This is why I think Apple has a real market opportunity if they choose to embrace it.
To this day I do not get why Intel doesn't just offer massive memory options for their cards. Just charge what it costs to add the extra memory, no upcharge, and they will never be able to keep up with demand. Cheap VRAM is enough to justify a lot of open source investment into challenging CUDA.
> To this day I do not get why Intel doesn't just offer massive memory options for their cards.<p>They seem to? Intel Arc is the cheapest option by far for a discrete card with 32GB VRAM.
They took longer than everyone expected and then shortly after release they made announcements that made people worry that Intel might kill the project the way they tend to kill GPU projects.<p>(I still kinda want to get one tho.)
That’s not massive, though. Make it 96GB at $2,000 (ok, probably impossible right now, but they could have before the surge in prices) and you’ll see developers work really hard to make AI tooling work for their cards, CUDA be damned. The same goes for AMD.<p>It’s like they both want to rely on market segmentation for VRAM too but fail to realize that it’s their only potential inroad right now.
Missed a zero here.<p>Needs 320 GB Vram
Memory is just one part. AMD has had offerings competitive to NVIDIA for quite some time, but nobody uses AMD cards.<p>The biggest advantage with NVIDIA is CUDA.
I have so many questions… Since Apple already sells unified memory systems, what is the market opportunity you envision? Do you see Nvidia and Apple as competitors, and how? (And I’m not suggesting they’re not, necessarily, but I want to hear where you’re coming from, and they do have very different markets.) Hasn’t Apple used storage size (RAM & disk) for market segmentation for decades? And how does a machine with 128GB unified mem not potentially cut into some people’s reasons for wanting a 96GB GPU?
I'm not the person you're replying to, but I wholeheartedly agree with them...<p>Quick background: doing AI inference requires three things. Lots of memory, lots of memory bandwidth, and of course plenty of compute that has access to that memory.<p>Quick reference: nVidia 5090 has 1,792 GB/sec bandwidth. 3090 gets about 1000 GB/sec. DGX Spark and AMD 395 whatever get about 275 GB/sec.<p>Apple M1 Max gets 400GB/sec, M5 Max gets 614GB/sec. Ultra variants get 2x that bandwidth, base variants get 1/2 that bandwidth. However... their <i>compute</i> is rather weak.<p>Right now, Apple's offerings are juuuuuust fast enough to run dense 27B models at usable speeds at like, 10% of the performance/watt of nVidia. They're world-leading general purpose CPUs but not killer GPUs.<p>By all accounts, these Windows PCs nVidia is touting seem to have DGX Spark like performance, which is less than impressive. Same with the upcoming AMD AI-oriented consumer stuff.<p>The <i>other</i> context here is that running your own AI at home is just starting to become feasible in terms of open model availability and the ability to run it at usable speeds. Many are interested in it for reasons of privacy, security, and cost certainty vs. buying tokens.<p><pre><code> Since Apple already sells unified memory systems, what
is the market opportunity you envision?
</code></pre>
nVidia and AMD <i>can't</i> make their consumer offerings too good at AI, because that risks interfering with their higher-margin data center sales.<p>(And, let's face it. Even if nVidia <i>did</i> release a 6090 with 64-128GB of memory for an affordable price, consumers wouldn't get their hands on them anyway because people would just start filling data centers with them)<p>So.<p>Now you see Apple's opportunity, right? No data center sales to interfere with. No relationship with nVidia or AMD to worry about.<p>They <i>could</i> choose to make an absolute beast of a home AI machine. The M5 Ultra, if announced, <i>might</i> be that. It's admittedly a niche market, but people are <i>already</i> buying 64GB+ Macs faster than Apple can make them and they're fetching high prices on the used market as well.<p>The only real questions are if this market is even something Apple would find time to care about, and if they could secure enough DRAM to make a go at it. They are enormous obviously but they're feeling the RAM pinch just like everybody.
They use different technology for their VRAM though. Apple, AMD Strix and NVidia DGX/RTX Spark use LPDDR, whereas discrete cards will be either GDDR or HBM. That directly impacts the memory bandwidth figures. As for compute available, Apple and AMD still have very good figures there for what's essentially a general-purpose iGPU that ships as part of the stock system, rather than a special-purpose piece of dedicated hardware.
There’s something else. Memory size.<p>Even if a Mac isn’t the fastest in raw numbers it may be faster if it can load the whole model in its ram (went up to 512 GB before shortages) than a couple 32 GB cards could with the data having to be constantly loaded over PCI-E. Because unified memory means the Apple GPUs can access all 512 GB at full speed.<p>My understanding is this is <i>the</i> advantage that’s pushing huge Mac Studio demand. Because it was the <i>only</i> way to give GPUs so much memory at price points anywhere near.<p>Yeah you can do way better once you’re in the 5 digits. But below that Apple had a specific advantage for some.
You're correct about some things but mostly wrong.<p>Yes, a Mac with 128GB+ will let you load some pretty big models.<p>However, you're still not going to be able to run them at usable speeds. Here are some M5 Max benchmarks on a Qwen 27B model w/ 290K context.... 12 tokens/sec output.<p><a href="https://www.reddit.com/r/oMLX/comments/1swztoh/m5_max_128gb_benchmark_qwen_27b_q8_mlx_290k_ctx/" rel="nofollow">https://www.reddit.com/r/oMLX/comments/1swztoh/m5_max_128gb_...</a><p>And that's a <i>27B</i> model. So yes, a M5 Max 128GB will let you load some pretty big models - can probably fit 120B in there with room left over for context. But the M5 Max still doesn't have the <i>compute</i> to make it practical, at least from an interactive usage standpoint - 120B dense model is going to be like an order of magnitude slower than 27B. You have to understand the computation going on here. LLMs are basically a huge many-to-many operation, and those operations themselves are pretty heavy.<p>So back to my previous post... you need three things. You need fast memory, you need a lot of it, and you need GPU compute with direct access to that fast memory. The M5 Max has like, 1.5 of the 3.<p>The M5 Ultra (if it ever exists) could kinda hit all 3, although actually getting your hands on one will be quite the lottery ticket.<p><pre><code> My understanding is this is the advantage that’s pushing huge Mac Studio demand.
</code></pre>
This is true, but also, people who made this investment found that they're still not very usable for those HUGE models. Don't take my word for it though. Lots of benchmarks out there. r/localllama is pretty active too.
12 tok/s can absolutely be "usable output" depending on what you're doing. I agree though that the 27B dense model often feels slow due to an overall weakness of memory throughput on that particular platform. Most real-world 120B models though will be MoE-based with only a small fraction of active parameters, and these run quite well. Also, dense models can benefit from batching, which is at least marginally viable with Qwen if you stick to shorter contexts and smaller batches.
Apple offers <i>relatively</i> affordable options for a high-memory workstation that uses unified memory. They previously offered 256/512GB Mac Studios (both discontinued). Because of this they can keep larger models in memory.<p>BUT you just can't compete with NVidia performance for LLM workloads (mostly inference) for two reasons:<p>1. The memory bandwidth just can't compete with a 5090 (1800GB/s). The best current Mac is ~900GB/s. That directly caps tokens/sec and might be manageable but there's another problem; and<p>2. The raw FLOPS just can't compete with even a 5090. It probably needs to natively support FP4/FP8 to at least maintain a number format parity with NVidia. But beside that, NVidia just has more raw FLOPS.<p>According to Google, an M5 Max does ~70 FP16 TFLOPS while a 5090 does 380. If Apple can close that gap to at least be competitive and also hold larger models in shared VRAM, that would be a competitive advantage and it would directly attack NVidia's market segmentation.<p>The Mac Studio last came out March last year. So we may get an update in Q3. Many are pinning their hopes on this. But it might not happen until next year. When it was released the M4 was the state of the art and it came with either the M4 Max or M3 Ultra (which, as I understand it, is basically 2 M3s stuck together, kind of). What people are hoping for is an M5 Ultra with >1000GB/s of memory bandwidth, ideally 200+ FP16 TFLOPS and hopefully FP4/FP4 support.<p>You can chain Mac Studios together into a cluster with TB5 too.<p>But it's reasonably likely that the next Mac Studio will be only incrementally better than the last generation.
Even low-VRAM cards are actually very useful for running the comparatively smaller dense layers in large local MoE models. This only requires transfering very small amounts of data across the PCIe bus (similar to pipeline parallelism) so it fits nicely around the existing bottlenecks on that hardware.
What should Apple do, in your view, to "embrace" it?
Mx Extreme = 2 x Mx Ultra = more cores. (Opportunity: processor chiplets could be designed to integrate in higher quantities.)<p>Increase RDMA cross-bar linking from 4x to 8x = a lotta ports, a switch, or a stacking interface.<p>Regular RAM size/speed scaling: 512GB -> 1TB Mac Studios. Wider RAM and RDMA paths * clocks.<p>Given the low power envelope of today's Mac Studios, and bandwidth limits, lots of room to scale up, if Apple chooses. My fantasy: 2x cores, 2x RAM sizes, 2x RDMA devices, 2-4x RAM & RMDA bandwidth.
> 5090 ($2k MSRP but realistically $3-3.5k)<p>These days, more like >$4.1K (at least in the US).
While I'm a supporter of Rust, I have to point out that Rust's memory safety doesn't help against side-channel attacks.
If this thing only has as much gpu bandwidth as the spark, it’s kinda pointles
Not true. This is aimed squarely at the Strix Halo and Mac markets. It's basically just strictly better than the Strix, and it's not clear cut vs that Macs in any sort of blanket statement.<p>My M5 Max 128gb MBP decodes faster than one of my Sparks, but the Spark's prefill is so much faster it can often answer the same query before the mac's prefill is finished. If you have large prompts, low cacheability, etc., a spark might be a very good options.<p>Not to mention you get can get two sparks and the MBP will be 85%+ of the cost at half the RAM.<p>I'm kind of tempted to pick one up. Leave running big models to my dual dgx setup, and all the misc. random stuff on an rtx.
Prefill will be a huge deal if batched unattended inference of SOTA models (on consumer platforms) becomes viable, because at that point it's the main remaining bottleneck. If running 30 inferences together boosts your decode throughput to 3x (that's consistent with some very rough experiments, though these haven't even looked at trying to mask SSD offload latency just yet), that's a 10x in total decode time but a 30x in total prefill time, because prefill workloads are fully compute bound already on consumer platforms and don't benefit from batching much at all.
Fair, but I don’t see what case you have w this. Mind sharing?<p>Seems niche to be both uncacheable and long context?
yeah, you only see double digits in performance degradation from going from pcie 5 to 3 with a 5090 (at x16 speed), with everything else its like in the single digits area.
And the thing we gamers forget is that <i>we’re the outlier</i>. We’re the edge case.<p>Most consumers will never really care about, let alone see, the difference in PCIe or memory bandwidth impacts from such a shift to unified memory pools. <i>We</i> might (being, at least in my case, a <i>huge nerd</i>), but I’m increasingly of the opinion that if modern blockbuster games are built for upscaling/reconstruction anyhow, then suddenly such sacrifices to performance seem acceptable relative to the gains in efficiency.
Well I mean, the idea with games is it all fits in vram. You really don't want to be thrashing. It's that things are still so slow that they must be avoided entirely, no?<p>No copy unified memory will help with that but you do pay the read speed costs.
gen3 is 16 years old.
This kind of post shows you have little idea why cpu and gpu are not sharing memory in the first place.
It’s also the reason, why you will never be able to repair or upgrade your computer in the future. From technological point of view these are indeed big advancements.<p>However, I couldn’t care less about faster CPU when:<p>1. It limits my ability to upgrade my system<p>2. Windows gets increasingly bloated and slower
> <i>The Unified Memory pool is the “game changer”</i><p>M1 knocking from 2020.<p>Gamed changed, past tense, six years ago.
This is catch-up.
Hell, SGI O2s from <i>1996</i> had this. For all of the hype the performance gains were pretty modest.
FWIW, the O2's UMA let it handle far more textures than almost any other contemporary system with reasonable performance.<p>Most other SGIs had single or low double-digit megabytes of texture memory, whereas the O2 could host one gigabyte of unified memory and use a huge chunk of that for textures.
UMA was never about performance and it still isn't. Spark is slower than a 5090.
did they learn why? were there other gains?
O2 GPU was slower than other SGI options at the time, however it could use hilariously larger pool of memory without copying, which meant that O2 could use approaches that were punishingly hard (very tight transfer loops) or impossible (huge textures that couldn't be virtualized due to needing <i>whole</i> texture).<p>That was because unlike other GPUs at the time, O2's didn't have dedicated memory but shared the memory with CPU - way slower, but zero copies and bigger.<p>Arguably early home computers and workstations also used "unified memory" :D
FYI it existed long before that. Shared memory between CPU and iGPU has been a thing for a long time.
I want unified but not uniform - everything can address anything, but you can add slower RAM to the system without requiring an entirely new chip. NUMA is cool.
AMD Fusion knocking from 2010.
Intel was doing UMA with their i740 graphics in the late 90s. Codename TIMNA was cancelled, but they pioneered it and used it on their you/cpu chips as well as their breakthrough 810 chipset that dominated graphics market for a decade. It was despised because it wa ubiquitous and a low performing graphics engine but games had to accommodate it.<p>Funny that it is getting credit only now.
> The Unified Memory pool is what will continue to be the “game changer” in systems architecture, especially outside of data centers.<p>The ps4 was the prime example of this, and how it could run so many great games.
> (which is good for Rust adherents, I figure).<p>As a Rust adherent, please do not put words in our mouths or set up unrealistic expectations for other people by linking together concepts at a very shallow level.<p>Language level memory safety has no answer for hardware security flaws which is what side channel attacks are. No programming language can provide memory privacy if another chip in your machine can read your memory. Just like no programming language can protect your application from a kernel vulnerability of the kernel it’s running on.
Damn. That wasn’t my intention at all, I was just pointing out that Rust has another reason to see wider adoption vis a vis the usual Valley advertising bullshit of deliberately conflating hardware security with software security. I personally give no fucks what something is written in, only that it’s written well enough that I don’t have to twist arms or babysit yet another sloppy piece of code in my enterprise.
But... it's rust.
"I am not sure how many people will run AI models locally. It still seems like a niche application to me. However, it will make decent machines to play video games."<p>I don't know who will be the winner but with some of the recent releases from gemma it seems more probable that you may run some models locally if only from a cost perspective, not even considering business security. Not sure how this type of architecture would make for good gaming though, puts into question the whole statement.<p>"Ranked in the top 2% of scientists globally (Stanford/Elsevier 2025) and among GitHub's top 1000 developers" - side note but this guy puts this everywhere, gives me probably the inverse of what he is marketing for.
"I am not sure how many people will run AI models locally. It still seems like a niche application to me. However, it will make decent machines to play video games..."<p>This is the 2026 edition of Ken Olsen:
"There is no reason anyone would want a computer in their home"
> <i>This is the 2026 edition of Ken Olsen: "There is no reason anyone would want a computer in their home"</i><p>Digging into this:<p>> <i>In conclusion, there is evidence that Ken Olsen did doubt the need for computers in the home, but the evidence is based primarily on the testimony of David Ahl who was perturbed when the personal computer project he championed at DEC was not supported by Olsen in 1974.</i><p>> <i>Olsen’s resistance may have been similar to that expressed by another DEC executive, Gordon Bell. In 1980 Bell thought home terminals would act as gateways to remote computers which would provide appropriate services.</i><p>* <a href="https://quoteinvestigator.com/2017/09/14/home-computer/" rel="nofollow">https://quoteinvestigator.com/2017/09/14/home-computer/</a><p>It was supposedly said in 1977: most computers at that time were not small, and so it would not be surprising that people would not expect the general public to desire a large, power-hungry, noise-y apparatus in their house.
That's exactly the point. Until recently, AI models that could run on home machines were so bad that it was very hard to imagine anyone wanting to.<p>And, like the overly large machines of 1977, models are getting faster, leaner, and better. It's happening a <i>lot</i> quicker, though.
This is why I'm bearish on Anthropic, OpenAI, and friends. I am not confident that we will continue to see the same pace of improvement in frontier model capabilities as we have seen over the past year or two - not using similar mathematics at least. But I think that getting results that are close enough to the same standard to be a realistic substitute but in a model small enough to run locally may well happen quite quickly. And if it does - where is the moat to defend these AI organisations with their astronomical budgets when they're already starting to price more realistically and that's already killing a lot of the hype they've enjoyed until very recently? They have an accidental moat because they bought up the global supply chain for storage but that surely isn't going to last once the data centres to hold that storage are becoming liabilities.
If model performance asymptotes and CPU/GPU and RAM keep growing, even slowly, then eventually we will have frontier models on desktop that are totally competitive with hosted. It’s only a matter of time.<p>You already can if you’re willing to spend many thousands of dollars on a beast of a machine. I’m talking about middle tier desktops and laptops here. Maybe eventually even phones.<p>The only way hosted stays strongly competitive in that world is if they can keep pushing the frontier or by playing the classic social media and SaaS games of network effect building and integrations.<p>Many people might still use hosted, of course, but what I really mean is that their multiples won’t be justified and they will have little to no moat. AI will become commoditized, like a sophisticated next generation form of an encyclopedia with search.
We kinda ended up with terminals connected to mainframes anyway. The terminal being the web browser, and the mainframe being SaS. So it wasn't that far off.
It doesn't really need this much explanation.<p>People take these quotes out of context all the time. Said in a business context, there was no need, at that time, for someone to have a personal computer.<p>There's no business justification in 1977 for a personal computer department at a business. It's similar to the gates quote about RAM (I think it was 64KB?).<p>These statements aren't meant to be forever quotes. Their business plan quotes.
> It's similar to the gates quote about RAM (I think it was 64KB?)<p>640, and Bill Gates said he either never said that, or at least never remembered having said it. I think there is no evidence anywhere that he did.<p><a href="https://www.computerworld.com/article/1563853/the-640k-quote-won-t-go-away-but-did-gates-really-say-it.html" rel="nofollow">https://www.computerworld.com/article/1563853/the-640k-quote...</a>
That exact quote? No, never.
He said something like: current computers at the time had 64kb of RAM, so the OS was designed with a limit of 640kb, and he believed this would give them 10 years of future proofing. As it happened, that limit was reached much faster, in about 6 years.
Or maybe he simply made a mistake. Big deal. This doesn't speak negatively of his other achievements.
He had a long career and presumably many successes, and is fallible like the rest of us. But a half-remembered zinger with no context makes for zippier posts I guess.<p>The early popularity of Minitel, the continued popularity of ssh/tmux, and the web browser itself indicates that bespoke client applications are not the only way. He wasn’t directionally wrong.
The simple explanation is that predicting the future is generally impossible. It doesn't matter if it's Olsen or anybody else.
I will not be spending thousands in hardware to run the worlds most mediocre llms at meh speeds. Sorry. I know for llm bros they think every output made by an LLM is magic, like every NFT guy thought every NFT collection was game changing, but there's nothing useful you can do with llms and 128gb of RAM (and there never will be) unless you have llm psychosis. Who cares.
Nothing isn't quite right but you wouldn't be using it like the hosted ones. 128gb is more than enough to run models to index my files and photos, denoise photos / AI photo masking, magic eraser type tasks for images, frame generation for gaming, etc.<p>Even for a lot of LLM type tasks, 128gb is likely more than enough to control a lot of PC configuration and automation with natural language.
or "640K ought to be enough for anybody."
<a href="https://quoteinvestigator.com/2011/09/08/640k-enough/" rel="nofollow">https://quoteinvestigator.com/2011/09/08/640k-enough/</a><p>Nobody ever said that, at least not as an assertion or prediction. The actual instances of similar language are from multiple people describing their earlier thoughts before they learned it wasn’t true.
There’s no public proof this has ever been said, and if it was, if it was not taken out of context.
I have that many browser tabs.
You seriously think running LLM is the same thing as general computing?
It’s better, it’s useful even for those who don’t have a deep knowledge of computers. I’d expect more AI users than programmers, than ms-word users, than excel users.
That’s too strong of an assertion.<p>Local models aren’t deterministically equivalent in capabilities to foundation models. Home computers are turing complete; just like a mainframe. They are just slower. Often not slower enough to matter.
Most people are ok with slower. An AI that lets you edit a family picture, in say 30 seconds, locally is preferable to one that is instantaneous but requires you to submit that picture to examination/storage/training/sale in someone else's AI ecosystem. If i want to crop my ex out of family photos, i should not have to first give that photo to Microsoft. If want an LLM to write a book report for me, i dont want it also alerting my school. And if i write a memo for a client, and i want an LLM to check the spelling, i dont want that memo leaked either.
It’s completely technically possible to have cloud services where customer data is opaque to the provider. Some of Apple’s services are like this already, for example.<p>I think there’s a sweet spot currently with munging your data blindly on the server so that your client device battery still lasts all day.<p>Meanwhile Apple and others push on with making client side models more efficient so that eventually the server costs and complexities go away.
I'd like to think so but the existence of Google and Apple and Microsoft's cloud based photo tools with phone integration suggests that's false.<p>You could run a pretty good home server on $50 of gear and yet we never saw any real adoption of OwnCloud/NextCloud style products as an alternative to Google Drive/Photos or Apple Cloud.<p>Why should LLM/Transformers be any different? Especially when you need a proper expensive GPU to run them instead of a Raspberry Pi?
Apple's photo tools run on device, and they'll probably ship more on device foundation models at WWDC too.<p>On-device AI is going to be important, I think. It doesn't have to take the form of a chatbot UI to be useful.
After the latest round of cloud storage price increases my non technical wife has been asking if we can do local backups instead...
> Most people are ok with slower. An AI that lets you edit a family picture, in say 30 seconds, locally is preferable to one that is instantaneous but requires you to submit that picture to examination/storage/training/sale in someone else's AI ecosystem.<p>Maybe if you ask them that question, but if you show them two products, they'll definitely prefer the faster one. 30 seconds is a long time to watch a progress bar.
Fast and public, or slow and private. Not everyone wants, or is allowed to, share their data with the AI world. And do not doubt that every bit shared with an AI service will be used for training.
The question here is about markets though. Not everyone wants x but if the vast majority of people want y, x is going to be niche and expensive.<p>You don't think the commercials of Google's AI photo features aren't going to have an impact on Apple users of their phones can do a worse version of that feature and it takes longer?
Plus there's the other question. If this thing is slower ... what's the price? The desktop/mini-pc version of this is $3000, after all. At this performance level what is an acceptable price for the laptops?<p>People definitely aren't going to accept more expensive + slower ...
He’s just a braggart. When you see something like this in somebody’s personal bio on social media, it’s basically a banner that means “take everything I say in the context of me promoting myself.”
Qwen 3.6 is far ahead of Gemma for most (but not all) things. I've deployed it out across a number of M5 MacBooks and it's genuinely useful for many tasks. It won't replace an Opus or current gen Sonnet sized model but it's still amazingly good for its size and probably as good as or just a bit before Sonnet 4 era. Far more reliable for tool calling, coding, agentic tasks and faster than the Gemma models especially with MTP.
Qwen 3.6 is a toy compared to DeepSeek V4 Flash or Pro. These models can now run on Apple Silicon hardware with as little as 32GB RAM for the Flash (with 2-bit quant, which is still quite capable) using SSD offloading, with just-about-reasonable performance for interactive use, and far better performance on longer contexts than Qwen (due to the more efficient KV cache/attention mechanisms in DeepSeek).<p>Very significant improvements may be viable for unattended inference via large-scale batches, which can reuse sparse experts and thereby mask some of the latency involved - this is quite unique to DeepSeek, again due to its efficient KV cache.
I've got a Qwen 3.5 running on a 12GB 3060 and it's dumb as a stump but still smart enough to get some useful work done. Since it's my daily driver desktop I havent jumped to 3.6 since last time I did I quickly ran out of vram and locked the desktop environment.<p>But yeah, the Qwen line is pretty impressive on commodity hardware.
I must be using LLMs very differently than y'all, because I can't think of a single thing I would rely on an LLM that's "dumb as a stump" to do for me.<p>To me, LLMs are for asking research questions + exploring design spaces + pointing at codebases to investigate bugs. And those all benefit from the model being as "smart" (in terms of both fluid intelligence and burned-in knowledge) as possible.<p>I'm guessing there exist problems where "intelligence past a certain point" doesn't matter, so these medium-sized models can match the performance of the bigger models. But what problems might those be?
Qwen suffers quantization a lot, rendering it borderline unusable.
The HN crowd is, by and large, not the target audience for his self promotion. I guarantee there is one and this is more or less effective.
> you may run some models locally if only from a cost perspective<p>I have a hard time believing running a model on a laptop will be cheaper than running it in a datacenter. Why wouldn't economies of scale apply here as with every other computation?
Does it apply for every other computation? Purely for the computation part?
You can host all kinds of things locally cheaper right now than in the cloud, no? (At least pre memory price hikes.)
It does, of course, come with its downsides like availability/reliability, less convenience, scaling options,..., but purely the computing price - I don't see why it wouldn't be cheaper in the future - at least for some use cases.
The datacenter setting has huge economies of scale for <i>low-latency, just-in-time inference using extremely large models</i>, but that's not the only viable use of AI. Batched, unattended inference of possibly smaller and weaker models, while theoretically viable in a datacenter setting, is far from the best use of that hardware. This is where local AI is at its best.
This is assuming that you'll be priced the fraction of computing that you consumed. But you are actually paying for their infrastructure, for the R&D (and also the computation that went into training the model) etc.
It is not clear that, for your own small computations, this kind of costs are needed, but you will still pay your share in the investment the provider made so that they could serve everyone's computation needs.
But, currently ... you're not. AI companies are operating at a loss, and are being subsidized by their investors.<p>Local may or may not be cheaper than remote now, depending on the details, but the factors you describe won't affect the math nearly as much as they will once that subsidization ends.
In that analogy bigtech AI is currently investing in cleaner air for all of us? We _could_ breath it through their hose, but might as well breath it outside.
A laptop is really a pretty bad form factor to run LLMs. Worst cooling, more expensive memory that you cannot replace, resell value depreciating fast. It’s fine for tinkering, small scale research, and demos but it’s definitely niche.<p>The vision NVIDIA is selling is pure marketing IMHO
Because economy of scale isn't really the right metric here. A machine you were you were going to buy anyway essentially has a TCO of $0.
It's cheaper <i>for the AI provider</i> to use your laptop instead of their datacenter.
What "every other computation"? I seem to have a lot processing power at my disposal here, between my cell phones, laptops, gaming PCs, various other hardware devices.<p>You're going to need to analyze the problem much more deeply because it sound like the standards you are implicitly applying would result in "economically, everything should be centrally hosted" but that is clearly not the result that obtains. Even a modern mid-grade cell phone is no slouch; you may not be running a current-gen frontier AI on it but you certainly can do a lot of other rather intense things locally that would have been laughable 10 years ago, like suprisingly high powered games.
I also don't get why this twitter user is linked here, versus all the news articles about this new hardware that have been everywhere over the past number of days.
The security aspect is the main driver why I’m seeing so many businesses investing in local hardware. They know the models aren’t as good (caveat that they also can’t run Chinese models) and that’s ok. Places that really care about security and data governance already aren’t on the bleeding edge. They wait for the nice stable lts version, they lock down dev machines in frustrating ways and have lots of IT admin layers.<p>But they also want to taste the sweet fruit of AI so the only way to do this that a CISO will approve is on local air gapped hardware. It’s a niche but still a billion dollar niche.
> not even considering business security.<p>I suspect personal privacy and need to run AI workflows to handle the litany of administration tasks of a household will be what result in regular need for local AI.<p>Apple is already out front with this on a personal, individual level, but they are not obviously headed toward multiuser/family-level ~biz admin with a persistent server running local LLM.
> this guy puts this everywhere, gives me probably the inverse of what he is marketing for.<p>Do you think he's in mensa too?
> "Ranked in the top 2% of scientists globally (Stanford/Elsevier 2025) and among GitHub's top 1000 developers"<p>This made me laugh. I can only image how insufferable this person is to deal with.
> However, it will make decent machines to play video games."<p>Where you will need games to be rewritten for ARM to get full performance, just like on Apple's M series chips.
Maybe they just mean from a "it can run a lot of DLSS" perspective.
I hope a family-level AI appliance is a thing later. Local non-cloud assistant that lives in the house, families interact via voice or phones or whatever. Knows the contextual family stuff you need, etc.
DeepSeek Flash v4 is the leading local AI on 128GB machines, and DS4 is still in preview (training not finished), no?<p>Especially on Dwarfstar.
Lots of people are already running AI locally. They are the people buying up all the consumer-grade nvidea gpus. What are they doing with them? Well, the same things people with home media or email servers are doing: stuff they dont want to share with the general public.
I want to reduce my dependency on companies like Google, OpenAI, and Anthropic. Aside from the concerns of data sharing I'm also not a fan of how they run their operations, for example Anthropic now using xAI's Colossus data center which is poisoning a marginalized community, or OpenAI getting in bed with the military.<p>Not everything I want to use an LLM for requires "PhD level intelligence", and increasingly I'm finding more uses that involve sharing my personal data.<p>Yesterday my local model helped me when looking for a doctor who is in-network for my insurance. I threw it a screenshot from the providers search results and it looked up reviews for all of them.
Which model are you running?
My local AI is currently upscaling an old british comedy from sub-dvd quality to 1k. (It is not availible other than on DVD.) It looks like it will take about a week for my pair of 5060s to chew through the task.
128GB seems the sweet spot for local models. I can program and install most GitHub projects with opencode and QWEN 32b with mtp.<p>anyone whose addicted to token theoughput is losing the operational knowledge and offline capabilities.<p>if you arent moving to the AMD 395 or MACs then youre hitching aride on the expensive calory ride
> "Ranked in the top 2% of scientists globally (Stanford/Elsevier 2025) and among GitHub's top 1000 developers" - side note but this guy puts this everywhere, gives me probably the inverse of what he is marketing for.<p>Lol yeah seriously, that stinks "I ask AI to generate a huge amount of bullshit and upload it to pad irrelevant stats".<p>Absolute loser.
I agree that it sends the wrong symbol, but actually Daniel is great. He cares tremendously about doing work that is actually real-world useful. I've co-written a few papers with him, and he's really hard working and open to outside suggestions. The danger is that if you send him comments, he'll eventually manage to rope you into writing a new and improved version. Seriously, if you are a non-academic computer scientist with a good idea that you want to publish, he'd be incredibly open to working with you.<p>As to why he now has this on his blog? I also cringe when I read it. I presume someone told him he should self-promote more, and this is his lame attempt to do so. He's almost certainly the most cited person in his department, but it's entirely possible that none of his colleagues actually know this. Cut him some slack. Self-promotion is not his strength. He's a nerd's nerd, and not a marketer. I'll mention to him that his attempt here might be backfiring when I'm next in contact with him.
I cringe calling it out but it just stood out as it was plastered everywhere and I actually have never seen his links before.
I kind of get it in the sense that every academic has to make themselves somewhat comfortable with self-promotion even if they don't like it. It's an important part of getting funding, but putting a blurb like that everywhere just hurts his credibility I think.
> As to why he now has this on his blog?<p>He doesn't just have it on his blog, he has it EVERYWHERE. Sometimes 2 or 3 times on the same page.
He's not a loser; he's done some really fun work that many people use daily. I've used his range mapping trick in multiple projects/papers. It's elegant.<p>It sounds like he's gotten bad advise about how to market himself /or/ this is being marketed to people who have bigger checks to write and whom he believes will be responsive to this kind of marketing. As an academic, it rubs me very wrong - I think it's detrimental to the field when we get into h-index stacking contests or citation count comparisons. But I don't know what incentives he's responding to, which seems important for putting this stuff in context.<p>(as an aside, it turns out that polars + fastexcel is about 10x faster than pandas + openpyxl for searching that dataset, if anyone else is curious what he was actually talking about. :)
I found his website, <a href="https://www.lemire.me/en/" rel="nofollow">https://www.lemire.me/en/</a> , and the "2%" brag is the very first sentence, geez.<p>Being the top x% is what OnlyFans girls brag about, professor...<p>And it's not exactly brain surgery, is it? <a href="https://www.youtube.com/watch?v=THNPmhBl-8I" rel="nofollow">https://www.youtube.com/watch?v=THNPmhBl-8I</a>
That lines looks very cringe indeed, but the guy has some crazy good blogposts on SIMD stuff.
I think the local-model use case is going to become less niche pretty quickly if the models keep getting smaller and more capable. Even if most people do not care about privacy or offline use, the cost argument is pretty strong
This feels fluff to me on the part of the author (whose work I don’t want to trivialize) but I don’t think they’ve actually looked deeper than a paper spec sheet on this.<p>1. Yes it has the same number of cores as a 5070 mobile. It’s also running at a shared peak of 2/3 the bandwidth and a shared peak of 2/3 the TDP. The GPU by itself will likely perform at half the dedicated units performance<p>2. Apple may not have SVE2 but they do have the AMX (private) and SME. I don’t see why he thinks the SVE2 will give him more performance than the SME.<p>3. He mentions a single core type but doesn’t mention the total makeup. We already have known for a year how the DGX Spark compares to Apple chips. For CPU it’s roughly equivalent to an M3 Pro and for GPU compute (not rasterization) it’s between an M4 Pro and M4 Max without considering bandwidth.<p>The real advantage to these is that they run CUDA. That’s it. Otherwise when they launch they’ll be 2-3 generations behind where Apple is and 1 gen behind AMD.<p>The other super power of the DGX Spark was the NIC for pairing them together. But that’s been removed here too.
> GPU compute (not rasterization) it’s between an M4 Pro and M4 Max without considering bandwidth<p>You are likely thinking about token generation which is dependent on memory bandwidth where Apple has an edge. Spark's GPU compute is way higher than even M5 Max (17 FP32 TFlops), around 2x FP32 TFlops... It's literally 6144 CUDA cores like desktop 5070, slowed down by slow memory and lower TDP (29.7 vs 31 FP32 TFlops on 5070).
Prefill is another advantage vs. Apple. It's way way way way faster on a spark than it is even on an m5 max.<p>Same model, same quant, same query, as close to as matched settings as I can get from vllm, and for workloads with large prompts + low cacheability, one of my sparks will often be done responding before the mbp is done with prefill.
Lemire is very narrowly interested in CPU SIMD so within that niche it may be interesting. As you said, overall the Spark is good but not great.
It is absolutely fluff, and the only reason this worthless tweet is on the front page of HN is that this audience has a habit of canonizing certain people, and treating each of their bowel movements as prophetic.<p>Guy suddenly became aware of a chip that the rest of the industry long knew about, seems completely unaware of the competitors, and posts about how it's a BEAST and will be a GAME CHANGER.<p>Like the DGX Spark was a game changer? Eh, it has mostly been a massive disappointment. An overpriced nvidia laptop isn't going to change the equation an iota.
The Qualcomm Snapdragon X2 Elite Extreme trounces Nvidia's chip in single core CPU performance. It beats Intel and AMD's best, too. It has unified memory. It's the only CPU in the same league as Apple's M-series in both CPU performance and power efficiency. And it's available in laptops today, not later this year. People are sleeping on Qualcomm.
Garbage operating system support. If you can’t do Linux support it’s a bit pointless because there’s two platforms for this that matter: Linux and Darwin.<p>Qualcomm is like AMD was for GPUs for like decades. Lots of announcements and people on the Internet are huge fans based on web pages they’ve read but if you try to make it work it’s a nightmare.<p>Snapdragon X Elite doesn’t work on Linux so it’s a pointless platform. Enthusiasts have made M1 work better. Literally have old Macs running rather than use Qualcomm.
It trounces ARM's old CPU design. The X925 used in this Nvidia chip is 2 years old. X930 or C1 has shipped with Mediatek Dimensity 9500 which is what the Snapdragon 8 Elite Gen 5 / X2 Elite should be compared to. Although Qualcomm still has a lead in performance, but it is increasingly shrinking.<p>But perhaps more importantly. Nvidia seems to be doing a lot better with its ecosystem. Nvidia has much better distribution channels and partners building on top of their PC Gaming GPU. It also have gaming developers relations that is unmatched by any in the industry.<p>Qualcomm has so far failed to execute this, both in PC and on there Server CPU side.
Microsoft is sleeping on Qualcomm with their lousy port of Windows to Arm processors…
I'm not sure they are sleeping. I have an older version and it can run games and other things just fine, its just over priced and not properly cooled. The driver/firmware support from Lenovo / Qualcomm is purely garbage. You're lucky to get a driver update to fix anything. For months it just overheated and video would start corrupting but that got fixed finally. You cant just go to Qualcomm's website and download new drivers even though it looks like you can - they really dont get how modern GPU's work on Windows - a driver updates to optimize for games is really something important because of how Windows is but the experience is pulling teeth. If the systems were Neo priced (500-700 USD) and had a cooling fan I'd be all on board with these systems. Right now, AMD with unified memory is just the better deal for the $1200 (2025) systems to run Windows and an average workload.
> with their lousy port of Windows to Arm processors…<p>What's lousy about it? I use it daily and have zero problems.
and is Qualcomm is sleeping on Linux?
Seems like not? Judging based on <a href="https://github.com/qualcomm-linux" rel="nofollow">https://github.com/qualcomm-linux</a> <i>something</i> is happening, although I can't say how much. They definitively seem awake at least.
The problem with these chips on Linux is that <i>something</i> has been happening for months but you still end up needing to download special editions of ARM Linux images to get these devices to work properly.<p>Some distros still need extracting Qualcomm firmware from Windows to get Linux to work properly. Audio remains a challenge, like x86 Linux decades ago. Apparently camera stuff works these days but produces images of subpar quality.<p>These issues also occur on normal Linux. My experience with my Lenovo+Intel laptop was that it took three months after release for the firmware to work properly (and the Nvidia drivers took much longer, but that's my fault for buying something containing Nvidia hardware). Intel managed to do what Qualcomm did in months rather than years.<p>I hope Qualcomm finally sorts this shit out, I really do, but with the prices of computers these days, I'm going to need to see quite the discount before I'll consider buying anything with a Snapdragon.
They run a hypervisor under the OS, and dont support actually running directly on the hardware, its very odd.
one of the biggest issue i see is the devicetree nonsense. It makes every single laptop and bios version very unique and requires a lot of housekeeping. There are also big chunks of work (as i understand it) to be done around hibernate and decent suspend support.<p>My experience (wanted to use x13s as daily sriver) is that there was good progress for about a year, until jhovold was leading the charge, but something expired and qualcom as far as i can tell forgot that some progress should happen on x1 and x8c as well as x2.
It feels deeply unfortunate that even with Windows on AArch64 requiring ACPI that it still doesn’t suffice for Linux, unlike on x86.<p>And I know a lot of that lies on the vendors, but it does feel unfortunate (from a standardisation/conformance/certification point of view) that Windows requiring it doesn’t make it easy to boot other OSes!
Yes, Ubuntu on the previous gen Snapdragon X is still trash.
10000000x this. They have been sleeping on Arm since windows phone. I just don’t see them ever having an original thought again.<p>They could have had a 128core arm chip by now.
They have original thoughts! It's just that those employees get squashed by other divisions or having to meet short term quarterly profits it seems.<p>There's also the whole giant trillion dollar company doesn't want to invest and let small ideas grow. They only focus on things that move the needle, which isn't much at the size.<p>Had Microsoft executed and invested, they could have made a come back imo in both search, mobile & hardware. Unfortunately major lack of leadership or they just don't want those areas.
Unless the chip was called Copilot, they are not thinking anything about it. If was called Copilot, they'd have already figured out how to shove it down your throat.
Qualcomm is a “fool me once, shame on you, fool me twice, you don’t fool me twice” kind of situation. So many horrible experiences in the past that people are going to be hesitant.<p>Qualcomm are trying harder now it seems. But it will take time to repair their reputation in the PC market.
They burned me with the first gen Snapdragon X Elite. Before the various laptops with it were out they promised Linux support. Here we are, years alter, still no fully OOTB support. Ironically, the GPU firmware were just mainlined in the kernel 4 months ago, but they still haven't done the same for the 1st gen X elite.<p>Tuxedo computers tried and didn't succeed either.<p>I will never buy Qualcomm again. I avoid them on phones as well by just buying Apple. They do not support their hardware beyond the release.
> I avoid them on phones as well by just buying Apple<p>To each their own, but I don't recall Apple ever mainlining any of their drivers on Linux. You're rightfully angry on the laptop side of things, but Apple is much worse than Qualcomm when it comes to open source support for their phones.<p>Qualcomm probably shouldn't have promised Linux support in the first place. Everyone seems to love Apple's hardware even though you're practically stuck with macOS. Had Qualcomm just stuck to Windows-only, they would've probably received a much better reception by the tech press.
Apple doesn’t sell general purpose computers outside of their own hardware so this doesn’t make any sense.
At least Apple tells you they don't support anything except their own OS, Qualcomm just pretends to offer support.
Can you say more? I don't have any memory of Qualcomm-related scandals(?), but I just read the news; I've never really been a user of their chips.
> Qualcomm are trying harder now it seems.<p>Not really, the 1st. iteration got stuck in legal land and other delays.
Is it well supported under Linux?
Qualcomm has been upstreaming Linux support for some of their chips but they're not working fast enough and I don't think the latest chips are there yet unfortunately.
I've been keeping an eye on the state of Linux on the first gen of X Elite and it's sad that the potential is not fully materialized outside WoA. Take a look at what peeps are going through:<p><a href="https://discourse.ubuntu.com/t/ubuntu-concept-snapdragon-x-elite/48800" rel="nofollow">https://discourse.ubuntu.com/t/ubuntu-concept-snapdragon-x-e...</a>
No, not at all, those machines are currently unusable on Linux.
Too bad Qualcomm provides shit drivers for Linux, never updates any of their drivers (had a Samsung/Qualcomm phone with drivers years behind the equivalent Google Pixel phone), etc... They are the absolute worst actor in the entire computing world, don't care how fast their chip is.
> X2 Elite Extreme<p>I'll wait for the 365 AI Ultimate Professional Enterprise Edition: Origins version
> People are sleeping on Qualcomm.<p>Technically speaking, Qualcomm acquired Nuvia, which is where this came from and that company came from ex-Apple engineers wanting to do what Apple said no for their chips.<p>So it's almost same CPU design (origins).
> And it's available in laptops today<p>Is there a desktop version ? For real work ?
People aren't sleeping on Qualcomm, they're tired of Microsoft Windows as a janky ass OS.
[dead]
[flagged]
Why do people care so much about single core performance? We are all professionals here and I bet most of our workloads are multi core. I get that these new arm chips from Apple and Qualcomm are great at one thing at a time, but for professional workloads high end x64 chips still cannot be beaten on the desktop.
I agree with you, but also:<p>outside of anything else, amdahls law means that as the parallel performance grows, we become _more_ limited by the inherently serial code, and thus single core performance, not less.<p>Given that single core performance is "harder" (can't just throw more cores/sockets at the problem), it's also critically important.
What x86 chips have the same or higher number of cores in the form factors that these chips are available in and are also more performant?<p>Strix Halo is 16 cores. Intel Core Ultra 9 285HX is 24. Apple is 18. Qualcomm is something similar too but I can’t recall. NVIDIA is 20.<p>Until you get to threadripper/epyc or Xeon territories (completely different form factors and TDPs) the arm chips are ahead on both power and perf than the x86. And even when you get to those areas, arm is equivalent or out performs them as can be seen by the recent neoverse x3 and Vera benchmarks.
Single core performance is the biggest factor for most day-to-day use of a computer, the stuff I do on a laptop. It's more important than peak multi core performance for web browsing and games. I only care about multi core performance when I'm compiling, and I usually do heavy compiles on a remote machine rather than on my laptop.
> Why do people care so much about single core performance?<p>Because that't the only part this chip excels.<p>People are comparing apples with oranges since ages.
Here is the press release for the actual machine:<p><a href="https://nvidianews.nvidia.com/news/nvidia-microsoft-windows-pcs-agents-rtx-spark" rel="nofollow">https://nvidianews.nvidia.com/news/nvidia-microsoft-windows-...</a><p>I have been somewhat surprised at the lack of commentators observing that this is <i>Microsoft</i> and above all <i>NVIDIA</i> launching a device that is fundamentally at odds with the metered cloud model of AI.<p>When you look at the other announcements and murmurings (better offline BYOK for Copilot, talk of an unmetered AI future) I think it’s clear that these two firms understand that cloud-only AI is not sustainable or inherently in their interests. But their willingness to undermine OpenAI with a product like this is notable.
Yeah, "unmetered intelligence" was probably the most used phrase at MS BUILD this past week. They are going hard into local AI
I don't think you can interpret this as anything other than a sanctioned rebuke, right? Everyone has a strong visceral sense for what that means.<p>Copilot just got proper "offline" BYOK support, didn't it? Presumably that was one of the things they were talking about. Though I imagine that has something to do with the fact that Zed has supported that properly for months.
Maybe. Or they are simply hedging their bets.
I do not see how it is a 'beast of a' anything. It has 300GB/s memory bandwidth, barely above AMD Strix halo (256GB/s) with the same 128GB RAM and less than half memory bandwidth of M5 Max 128GB (614GB/s). Emphasizing memory bandwidth because most people interested in it I suppose are AI enthusiasts. Also, Windows.
Unlike the M5 Max, it should have usable context prefill. It's feasible to run 256k token workflows that would take the better half of an hour for TTFT on the M5.
They have a lot of software groundwork ahead of them to make an ARM CPU viable for any kind of desktop use outside direct inference or training usage too.<p>AMD has the advantage that their x86 machines run everything, Apple maintains the whole MacOS stack, while Nvidia can barely scrape together one Ubuntu release per Jetson generation, it's beyond embarrassing. Maybe they ought to put those agents they keep droning about to some actual work on their OS support.
> Nvidia can barely scrape together one Ubuntu release per Jetson generation<p>Why would they do more? It's an LTS distro, the Nvidia drivers are updated for as long as the hardware's compute capability is supported.<p>Nvidia's ARM drivers are updated constantly, and battle-tested as the backbone in hundreds of thousands of Grace ARM servers.
I think most people are not understanding what this kind of laptop will provide.<p>Before we get local AI, we'll be using hybrid AI.<p>Running big models locally is unrealistic ($$$$$) but, if you imagine an Agentic Workflow where some bits run on the cloud and other smaller tasks locally, it's an amazing deal. You don't need Opus/Code/DeepSeek/Kimi/etc to do basic stuff that models like Gemma4:12b/Qwen-27b can do locally with much less latency.<p>Having a laptop where I can use a remote big model and combine it with 5 local domain specific models, is something I would love to do today. Imagine using OpenCode and you've a small model deciding which tasks run locally, then decides if you've a good local model for XYZ task or if we use a cloud model.<p>My main concern is: Is this hardware powerfull enough to allow local quick models switch? Unlikely but I hope I'm wrong
Given the incredible progress of local models, on present trajectory I think we see comparable levels of performance to frontier models in two years on 128GB unified RAM and 6-bit quantisation. Note how the frontier models are now hitting superior benchmarks with only 200,000 tokens. I think we still have a long way to go with distillation.
And who in 2026 is still anal-fixated on a "Windows" PC?<p>It's just a personal computer. It normally runs multiple operating systems just fine.<p><i>Windows</i> PC sounds like people talking about tech who are either payed by M$, or embed pictures into Word documents to send them.<p>Nobody has to kill the fun those OS agnostic machine allow, by artificially bind them to a shitty OS.
Enterprise, of course. They probably buy more PCs than the rest of the market combined.<p>Even for personal use, I'd imagine the amount of people dual booting Windows and something else are a very tiny minority.<p>Saying "Windows PC" is a pretty reasonable way to distinguish between "made by Apple" and "made by someone else" because the market of PCs that aren't made by Apple and <i>don't</i> come with Windows is really, really tiny.<p>To be honest, this seems like a strange hill to take such an aggressive stance upon.
> <i>And who in 2026 is still anal-fixated on a "Windows" PC?</i><p>I'm assuming it's just clarifying this isn't about Macs.<p>The term "PC" is ambiguous, since it can either refer to <i>all</i> personal computers in its original meaning, or to the IBM PC lineage that is mainly contrasted with Macs. Remember the famous "I'm a Mac, I'm a PC" ads.<p>When you just say "PC", people today <i>genuinely</i> don't know which meaning you are referring to. And "IBM PC" is antiquated, and "IBM PC clone" is even worse. So "Windows PC" is a pretty decent name.<p>Do you have a better suggestion? Because "Non-Mac PC" doesn't exactly roll off the tongue. If you say "Windows PC", everyone knows what you mean.<p>And it's not an "anal fixation", there's no need to be gratuitously insulting.
Well, there's the other problem, windows sucks.<p>I prefer Windows XP, or even Windows Vista, to Windows 11 with its copilot. And it's been a downhill race, even macs are more of your own personal machine than Windows today, which is saying a lot.<p>PC should be a PC, Windows is as they advertised, a Copilot PC.
Hopefully anyone who wants to run anything other than Windows on an Nvidia-produced device has learned their lessons at this point. Although, a cursed Nvidia Hackintosh would be extremely funny.<p>For normal people, there are three computer operating systems: Windows, Apple, and ChromeOS. Nvidia isn't going with ChromeOS and Apple hates their guts, so Windows is the only normal operating system they can market.<p>Their marketing makes clear that these devices aren't the piddly Chromebooks that ruined the desktop experience for so many people (expensive Chromebooks were nice, but rare in practice).<p>Qualcomm promised Linux support, failed to deliver, and now anybody burnt by their promise won't want to buy their hardware again. If they promise a Windows PC, people won't have reason to complain when Linux or FreeBSD or SerenityOS won't boot on there. Given Qualcomm's failures here, Nvidia is probably doing the right thing.
> Although, a cursed Nvidia Hackintosh would be extremely funny.<p>I did this for years. We ran Resolve color correction suites with external chassis to place multiple Nvidia GPUs in it at a fraction of the cost of the shitty TrashCanMac that was available. Lots of people continued to use the 2012 Cheese Grater MacPro with its older CPUs. The only way to get modern (at the time) compute in a Mac was to use a Hackintosh. Since it wasn't for personal use, not having things like AppStore, Messages, Music, etc wasn't a big deal, so building a Hackintosh was easier.<p>I built one for personal prosumer use around the time of the 1080s that allowed me more machine for the dollar than Apple offered. Once the M-series chips came out and they were capable of what the Hackintosh was doing for me put me off of building anything newer.
Windows is dying a death by a thousand small, user-unfriendly decisions. This is genuinely sad because the technology underlying Windows is actually very robust and flexible.<p>So, the partnership is maybe natural, but not prospective. Also, note how Linux is getting popular among gamers. Of course, it's way behind Windows, but the direction of the change is clear.<p>I'm convinced that Nvidia is not primarily targeting the consumer market and that the ultimate goal for its CPUs is the server space. The company invests effort where the money is, and consumer products account for only a fraction of its total revenue. Maintaining a presence in the consumer market seems more like a way to avoid a complete pivot than a strategic priority.
And this isn't a "Windows PC" in the traditional sense. The reason people run Windows in the enterprise (and for some desktop home uses like games) is still hardware and software compat.<p>I run it for work because we make windows programs. We use drivers that don't exist on Win-for-ARM yet. So to most people a "Windows PC" is an x64 Windows PC still. The risk for MS if compat isn't good enough for Windows-Arm64 is that people might as well shift from windows entirely if they need new software and harware anyway.
A big push specifically for <i>Windows</i> ARM from Nvidia seems like relevant information.
> It's just a personal computer<p>Your x86 machines were, but these are ARM SOCs. Many of them don't even support UEFI, let alone the upstream Linux kernel.
The interesting part to me isn't really the Cortex-X925 vs AVX-512 comparison, but Nvidia trying to make the GPU the center of a Windows PC rather than an add-in card
I don't think this is going to get any traction in the general consumer world, even less relevant than Apple Vision Pro.<p>(HN reaction to Vision Pro back in 2024 is almost hilarious if not ridiculous, looking at it today. I knew it would be a flop and I was so right.)
Wild that it took me so much scrolling to find some sense!<p>Spark DGX also remains a nothingburger, I would be livid if I spent this kind of money and had to waste time chasing down power cap bugs or A/B/C testing each firmware version to find the one that is least slow and also does not fail <a href="https://dredyson.com/the-hidden-truth-about-dgx-spark-performance-degradation-gpu-power-draw-issue-what-every-developer-needs-to-know-about-the-14w-power-cap-bug-proven-workarounds-and-the-complete-diagnostic-guide-t/" rel="nofollow">https://dredyson.com/the-hidden-truth-about-dgx-spark-perfor...</a>
<a href="https://xcancel.com/lemire/status/2062880075117113739" rel="nofollow">https://xcancel.com/lemire/status/2062880075117113739</a>
I follow Daniel Lemire and like his contributions, I also understand that the HN thread was created for discussion purposes, but I'd really appreciate having a reference to the spec or a source to the claims made, either here on HN or on the tweet itself.<p>I dislike the cycle of propagating news and assuming that someone else double-checked it.
I think you’re asking for <a href="https://nvidianews.nvidia.com/news/nvidia-microsoft-windows-pcs-agents-rtx-spark" rel="nofollow">https://nvidianews.nvidia.com/news/nvidia-microsoft-windows-...</a>:<p><i>“News Summary:<p>- NVIDIA RTX Spark powers the world’s first Windows PCs purpose-built for personal agents, featuring 1 petaflop of AI performance, industry-leading power efficiency, full-stack NVIDIA AI and graphics technology, and up to 128GB of unified memory.<p>- NVIDIA and Microsoft collaborate to deliver a native Windows experience for personal agents, including new security primitives and NVIDIA OpenShell to run agents securely on primary devices.<p>- RTX Spark lets creators, AI developers and gamers render ultralarge 90GB+ 3D scenes, edit 12K 4:2:2 video, generate 4K AI videos, run 120B-parameter LLMs with up to 1 million tokens context using agents locally, and play AAA games at 1440p and over 100 frames per second.<p>- Adobe is rearchitecting Photoshop and Premiere from the ground up for RTX Spark to deliver 2x faster AI and graphics performance.<p>- RTX Spark-powered slim Windows laptops with all-day battery life and premium displays, as well as compact desktop PCs available this fall from ASUS, Dell, HP, Lenovo, Microsoft Surface and MSI, with models from Acer and GIGABYTE to follow.”</i>
I can't really see wide adoption of local LLMs unless prices really start to climb. It makes sense to use cheaper hosted smaller models like Sonnet or even Kimi but these won't run a Kimi-class model and that is really the floor for non-toy agentic tasks. Spending 5k to avoid a $20 subscription really only makes sense for niche security reasons.
I'd bet on the inverse: China scaling DRAM production until the price crashes, and the whole US stock market that is propped on top of that scarcity going down with it.
I think we really haven't even seen how GenAI can influence new products and games. Have you consumed Dungeon Crawler Carl?
The same chip that's been available in the DGX Spark for like 8 months now...why are we pretending like its the next big thing.
nb: poster is Daniel Lemire (<a href="https://lemire.me" rel="nofollow">https://lemire.me</a>), who is very skilled in getting performance out of compute hardware (e.g. via simd, cache usage etc)
As he likes to share often, "He ranks among the top 2% of scientists globally (Stanford/Elsevier 2025) and is one of GitHub's top 1000 most followed developers. "
Still, Microslop has repeatedly proven their ability to slow everything down to a crawl no matter how powerful the hardware. If you want it to be fast, don’t use Windows.
The commenters here seem to have forgotten that computers can do things other than inference
Is it really unified memory? AMD Strix Halo is "unified" but you still have to allocate memory separately for cpu vs gpu. Apple Silicon is true unified memory.
My understanding is that this is the limitation from Windows not from AMD SoC. There are several internet resources to "enable unified memory support" on linux eg [1].<p>As a side note, qualcomm chip set on Android has been doing this for years (like Apple) so it's not super unique thing. It's more like there was no need before.<p>[1] <a href="https://www.jeffgeerling.com/blog/2025/increasing-vram-allocation-on-amd-ai-apus-under-linux/" rel="nofollow">https://www.jeffgeerling.com/blog/2025/increasing-vram-alloc...</a>
Even then the "reserved" section is a carve out guaranteed chunk to allow stuff that might need contiguous physical memory (display scan out buffers and page tables, for example) and similar.<p>The GPU can still happily use all the rest of the memory for other use cases - which tend to be the bulk of allocations anyway. Though there might be performance implications - for example "moving" buffer ownership to the GPU would need to evict CPU caches, and often 4k pages and tlb lookups can be a pretty inefficient situation for GPU-style accesses.<p>That's been pretty standard for any SoC for decades. And "differences" to apple's SoC are more implementation details.
yes, but more due to OS limitations than hardware. You can use their GTT which is then _true_ UMA where GPU can grab whatever it wants from the memory pool.<p>This isn't the first time we have UMA on the PC, btw. When SGI did their PC workstations, their 320 and 540 PC workstations had what they called Cobalt graphics chipset and crossbar with their IVC architecture. They bypassed AGP at the time completely. It was quite unique to see strict UMA on a PC. Haven't seen it since until these new systems we're seeing now on PCs and Mac.
That's a software question, not a hardware question.<p>Some software assumes pre-defined set-aside pools of memory reserved for video purposes, but the chip does actually have access to the whole pool.
For local models, the useful part is not just having 128GB attached to the package. It is whether the GPU can practically use that memory without the usual VRAM-style constraints
Strix halo is unified memory. The memory allocation set in BIOS is overridden by the operating system if it has the capability.
Memory bandwidth is what matters, unified or otherwise. Discrete GPUs don't have unified memory either.
> you still have to allocate memory separately for cpu vs gpu<p>That's an API issue not a hardware issue. Regardless, I believe the major APIs permit seamlessly sharing pointers at this point? (I have no experience doing that though.)
<i>>AMD Strix Halo is "unified" but you still have to allocate memory separately for cpu vs gpu.</i><p>IIRC that's due to maintain BIOS and Windows (+games & apps) backwards compatibility, but memory access speeds are the same.
It is unified in the sense that the OS can dynamically assign memory to CPU and GPU. Apple silicon is not a alien tech that other silicon vendors cannot implement.
How is this different from something like the AMD Ryzen AI Max that can already be purchased and supports 128GB unified memory? Seriously curious.
I dont really get the hype with all the N1X thing when in reality this is the same almost 1 yr old GB10 that was released with the DGX Spark and proved to be quite a disappointment
It’s an opportunity for them to start doing away with the whole ATX thing where owners had freedom to mix and match at their own pleasure.
I really hope this will have proper GNU/Linux support, otherwise it will end up the same way Qualcomm ARM PCs did.
A beast if a Windows PC to do what? Run Trams, Excel, Outlook, and a browser all at the same time? We could do that just fine in 2010…
Just give it a year or two and Windows will drag that sucker into the mud and run everything just a sluggish as ever.<p>The idea that any hardware performance increase will be eaten up by terrible software is an evergreen. A computer that could serve as the single server for a medium size enterprise 20 years ago, is no longer able to serve as a desktop for a receptionist. I'm not even sure we're talking diminishing returns anymore, we're probably past the point of maximum yield and into the negative returns at this point.
> up to 6,144 state-of-the-art CUDA cores<p>A RTX Pro 6000 has ~24K 5th generation tensor cores, I'm guessing this would then be 1/4 of the count but 6th generation? Wasn't clear from the images.
Why is it only for Windows PC, can we not run Linux or at minimum SteamOS?
I ran two gens of Jetson board and I have zero confidence in this. NVDA is printing in the data centre and everything else has no staying power.
Offtopic, but "Twitter. Now that's a name I've not heard in a long time. A long time".
How much is this supposed to cost, fully populated with 128GB of RAM? How much would this laptop cost?<p>It's not that the NVidia chip has that much RAM built in, after all. It's that it can address that much. RAM is sold separately.
The dgx spark is the same chip and those are in the low 3s to 5 range for most of them depending on manu, storage config, etc. The dgx sparks also have connectx 7 cards in them to support the 200gbps networking for RoCE.<p>So I would expect the mini PCs to come in less than the sparks. Laptops I assume will be close in price with the addition of all the other laptop stuff.
No. It’s all integrated. Not something you can buy separately or upgrade later.
See [1]. There's not 128GB of on-chip memory. "Integrated" memory in this context means that the GPUs and CPUs all use the same memory. There are on-chip caches, of course.<p>[1] <a href="https://www.nvidia.com/en-us/products/rtx-spark/" rel="nofollow">https://www.nvidia.com/en-us/products/rtx-spark/</a>
$4,000-5,000
If it runs well with Linux, I’m sold. A Windows pc will never see the inside of my network.
The DGX spark desktop shipped with Ubuntu, but I haven't seen if it has a bunch of Nvidia specific repos for drivers etc. needed to make it function.<p>Assuming all that stuff is upstreamed (and they aren't using oddball webcam/input devices etc) it should have much better support than Qualcomm.<p>Fingers crossed!
It's effectively the same as the GB10 in the DGX Spark (Blackwell architecture, 6,144 CUDA cores, perf-wise comparable to an RTX 5070).<p>I've found it very useful for running big models, but it's not a screaming powerhouse in terms of raw compute.
> “Our goal is to deliver unmetered intelligence to every home and every desk with Windows,” said Satya Nadella, chairman and CEO of Microsoft. “RTX Spark marks a real breakthrough towards that vision.”<p>I expect computers with this chip will be about $4000. If Microsoft can deliver on local AI models that can orchestrate Windows and have solid real world intelligence, that will be an inexpensive business purchase compared to pay as you go tokens. I'm excited to see how this plays out.
Says running local llms isn’t relevant. Than says it is decent for games, which is just correct if you compare any gpu remotely similarly priced. I don’t understand what is the point he is making
Sounds good, but how much does it cost? Is this going to be an affordable laptop or $6000.
SGI had unified memory back in 1996.
Is this essentially an Apple M-Series chip in concept?
No, it stems from a lineage of Tegra chips that pre-date the M-Series.
This chip <i>was</i> called GB10. One of its predecessors, GV10 was shipped in 2018.
It was a 256 bit, unified-memory system on a chip with a Volta GPU and 12 ARM Cores. GB10 is a 256 bit, unified-memory system on a chip with a Blackwell GPU and 10+10 ARM cores.
while unified memory may offer better performance than unsoldered DDR system memory, it still won't be as great as 1.8TB/s bandwidth on high end consumer GPUs right now.<p>nvidias master plan may be making it the new normal to have "only" 400GB/s bandwidth, thus gatekeeping local model usage further behind "more memory but not as fast as the cloud can do it"
I think it’s an interesting theory but a bit too conspiracy theory-ish.<p>Nvidia just wants to sell stuff to everyone.<p>And I think for professionals doing local AI work, products like Strix Halo and Apple Silicon are a competitive threat.<p>A big part of maintaining the leading software ecosystem is ensuring you have competitive hardware for all your users.<p>I also think the RTX Spark product is relatively low effort for Nvidia. Grab a Mediatek CPU and slap an Nvidia GPU on the die. Sure, that’s oversimplifying it, but still.
The M1 Max from 2021 has better memory bandwidth. The M3 Max can be specced to 128GB.<p>Nothing new here, apart from being able to use CUDA on a less power hungry system.
The M1 Max has an unusably slow GPU for inference. TTFT on real-world contexts can be over 10 minutes.<p>> Nothing new here, apart from being able to use CUDA on a less power hungry system.<p>CUDA has been running on ARM SOCs since the Tegra K1, 12 years ago. Nvidia is not new to ARM, nor is CUDA.
128GB of unified memory is a dream come true for local LLMs. VRAM has been the ultimate bottleneck for developers.
The competitor for this NVIDIA CPU will not be the now old AMD Strix Halo, but its successor (launched recently), which supports up to 192 GB of unified memory. Thus 128 GB is no longer SOTA.<p>While this NVIDIA system is inferior from the point of view of the memory capacity, its main advantage is that the top models will have a bigger GPU, i.e. with 6144 or 5120 FP32 execution units, compared to 2560 for the AMD GPU (compared to the NVIDIA CPU, the AMD CPU has a better multi-threaded performance for legacy programs, and a much better multi-threaded performance for the applications that use AVX-512).<p>However, these top models with big GPUs will also be much more expensive than the competing AMD system, while also being much more expensive than a laptop or mini-PC with an equivalent discrete NVIDIA GPU (which has the disadvantage of having direct access only to a much smaller, even if faster, memory).
I have a 128 GB LPDDR5X machine. It's a great workstation laptop (which is why I got it) but the memory bandwidth is just awful if you're wanting to use it for AI. An old Epyc CPU will fair better both in terms of being able to run full sized larger models as well as having higher memory bandwidth, and that's not a recommendation to go that route either as it's still not worth it.
It could help with exploding external LLM costs.
Interesting to see how the adaption will be, which will mainly depend on the price.
This is what makes it interesting to me as well
[dead]
It's just a DGX spark with faster memory and a windows boot?
good to know, hope the price will be affordable, having a pc becoming a luxury :)
I’m not sure if you’re aware but there is a supply chain shortage for pretty much everything needed for a PC that isn’t expected to be solved this year or next year. There is no way that can be affordable
Certainly not in the year of our lord, 2026. Maybe in a few years though.
Mediatek and Nvidia the horsemen of abandoning hardware after a year. The Jetson family still left a bad taste in my mouth.
Qualcomm is too. They mainlined the GPU firmware for the X Elite 2nd gen, but still have not done so for their 1st gen X Elite which they promised full Linux support for and failed to deliver, and have now moved on pretending they never said that.
How dare you question the golden goose egg-laying algorithm for trillions in stock valuation!
Don't want to be too harsh, maybe I'm missing something, but the CPU is at least 2 years old, internally it has been a complete shitshow and that's a minor hiccup when compared to the firmware and software situation.<p>It's an interesting "newcomer" and the more the better but calling this a "beast" and a "game changer" is ridiculous to say the least.<p>Then there is the price..
Can it run Ubuntu?
Yeah when laptops are shipping 8Gb and Microsoft is suddenly interested in native apps, nope.<p>Tech companies have strangled their own market.
Is this somehow satire? This is just the dgx spark with keyboard and monitor in a convenient format. Since it has more stuff, I'm sure that the price mark up will increase too.<p>Up to $5000 because why not?<p>With that money you can build a real PC with rtx 5090!
> The game changer is the unified 128 GB memory. That is the path Apple took years ago. Instead of separate memory for the CPU and GPU, everything shares a single pool. It is increasingly popular.<p>> The memory is not as fast as dedicated GPU memory, but it is cheap enough while delivering enough bandwidth to run AI models locally.<p>So, the reason "dedicated GPU memory" is fast, isn't <i>because</i> it's "dedicated"; it's because the types of memory built into GPU cards — GDDR and HBM — are designed for throughput over latency.<p>Which is to say, GDDR and HBM memory <i>could</i> be shared with the CPU in UMA while still being "fast" (for GPU use-cases.) In fact, the PS4/5 and Xbox 360 / One X / Series consoles have UMA architectures that use GDDR memory <i>as</i> their main memory, with no regular DDR memory to be found.<p>What I don't understand: why don't we see UMA architectures where there's <i>both</i> regular DDR <i>and</i> GDDR/HBM memory mapped into the address space of the CPU+GPU? That seems like the best of both worlds: you'd have some memory that's "tuned" for random-access CPU usage (regular DDR), and some memory that's "tuned" for streaming GPU usage (GDDR/HBM), but either type of memory <i>can</i> still be put to the use it wasn't "tuned" for, just with slightly-worse performance.<p>I guess you'd need to do a bit of software work:<p>1. a bit of work in the OS kernel / malloc library to get CPU workloads to "prefer" allocating DDR memory over the GDDR/HBM memory until they've exhausted DDR memory (or maybe not, if you just tell the kernel the GDDR/HBM memory is something like a zswap thinpool);<p>2. and a bit of work in supported ML frameworks, to teach them about a hybrid strategy between UMA "allocate anywhere, it's all the same" and NUMA "keep assets in VRAM if possible; if you spill assets to RAM, then they must stream into VRAM on access" (i.e. "at allocation time, allocate as if the system were NUMA, VRAM first then spilling to RAM; but at execution time, use the UMA codepaths, no need to copy RAM into VRAM.")<p>...but once that's done, it's done.
Theoretically, maybe? But they are completely different interfaces so it would surely get complicated. It's also approaching the current behavior in non-unified memory systems where you have two pools of memory with different performance characteristics. You'll realistically want the CPU to always use low latency memory and the GPU to use high bandwidth memory with very little moving between them.
They are useless if RAM prices are this high. $800 laptops with maximum 8GB are currently the norm, Windows 11 can't run on them decently. No matter how fast the SoC is with overpriced RAM they are slow. Systems that can make good use of them with 64-128GB are not affordable anymore thanks to Nvidia and co. This is a smokescreen. They'll probably sell them packaged as compute modules anyway.
It's going to be amazing. Almost twice as fast for only 10 times the heat. Consumers aren't concerned with efficiency they only care about performance.
Related:<p><i>A powerful new chapter for Windows PCs, accelerated by Nvidia RTX Spark</i><p><a href="https://news.ycombinator.com/item?id=48352693">https://news.ycombinator.com/item?id=48352693</a><p><i>Nvidia RTX Spark</i><p><a href="https://news.ycombinator.com/item?id=48352939">https://news.ycombinator.com/item?id=48352939</a>
A hardware company that propose to buy more hardware from them.<p>Must be a new business model.<p>....<p>Step into my office<p>Why ?<p>Because you are fucking fired
They announced RTX spark days ago. Why is this post linking to a "leak" tweet on the frontpage now?
Not gonna lie, I'm buying one of the 128GB ram ones for local inference if price is human.
Wait a minute!<p>Nvidia going from GPU to CPU now?
This is the RTX Spark [1].<p>The obvious comparison here is the M5 Max where you can buy a Macbook Pro with 128GB of also unified memory. Obviously CUDA cores are specific to NVidia so it's hard to directly compare but I've seen claims that the M5 Max is roughly equivalent to ~4000 CUDA cores. This obviously depends on workload and whether the CPU supports the precision you want to use (eg FP4).<p>The M5 Max has memory bandwidth of 819GB/s. The RTX Spark I believe is ~600. So it might be slightly better than the current generation of Macs but likely worse than the expected M5 Ultras of the new Mac Studios (likely Q3 2026).<p>For comparison, a 5090 has >20k CUDA cores and 1800GB/s memory bandwidth with 32GB of VRAM. The RTX 6000 Pro (at ~$10k) has 96GB of VRAM, same bandwidth and ~24k CUDA cores.<p>We have to see what RTX Spark systems sell for but the DGX Spark is in the Mac Studio price range (~$4k).<p>I do think Apple has a real opportunity here but there offerings aren't quite there yet. The M5 Ultras might be a really attractive option for local LLMs. I expect them to be in high demand.<p>[1]: <a href="https://news.ycombinator.com/item?id=48352939">https://news.ycombinator.com/item?id=48352939</a>
> I've seen claims that the M5 Max is roughly equivalent to ~4000 CUDA cores<p>Who claimed that? The M5 is still a raster focused GPU, dedicated matmul blocks be damned. For some workloads that napkin math might work out, but for many others it's a wild overshoot. Time-to-first-token still favors CUDA, and real-world training workloads aren't getting anywhere near Apple Silicon.<p>All of the memory bandwidth in the world is useless if you spend 15 minutes processing 64k tokens worth of context prefill. This is where CUDA shines.
Will it support Linux?
Are their enterprise orders slowing down? Why use precious maxed out fab capacity on consumer stuff when it could be an enterprise chip?
It uses LPDDR5X instead of VRAM and will still sell for a premium while pushing their presence even further in every side of the AI market. This was one area AMD was ahead in and now Nvidia is probably better off making this to compete on that front while still being better off than making a 5090.
It already is an enterprise chip. This is about Microsoft not having the equivalent of an M3 Max or whatever laptop.<p>And maybe for NVIDIA and MS it is also about them quietly betting that local models are, in fact, going to be good enough for most tasks pretty soon.
This is an enterprise offering. It'd take a guess its to try and stop the bleeding over to macOS. This launch, plus WSL containers, their own de-bloat winget config, mxc, etc. all seems like they're saying "pls stop leaving for macOS, see, Windows can be a great dev machine too."
This chip was designed before the shortages. I think they'll order just enough units to say they released it but not enough to put a dent in Rubin.
<i>I am not sure how many people will run AI models locally. It still seems like a niche application to me.</i><p>I'd say this relates directly to the cost of running AI models remotely.<p>And we won't know what the actual cost will be until AI vendors recover the huge pile of cash they've dumped into development (plus interest).
I think it's niche now because getting the hardware to run it is expensive and the quantized models don't work as well. If those improve then it would be a no brainer to pay one off for the hardware instead of a fortune for API calls.
I am not really convinced that four bit quantisation is that bad; almost certainly six will be enough. But Google are making claims for their QAT tech in Gemma that they are surely using or testing in Gemini that it preserves nearly source model quality while reducing footprint.<p>The hardware for 50 tokens per second with a four bit quantisation of Gemma 4 26B or the sparse Qwen 3.6 is not really that expensive: it’s a secondhand M1 Max.<p>Beyond that, I agree. I think moving planning tasks to local is a now thing, not that it really has much impact on token spend. I also think many small coding tasks are fully within the grasp of the above two models.<p>The main issue right now is that the software landscape is rather confusing, but I reckon uncomplicated Gemma 4 26B QAT support with MTP is a few weeks away.
AI vendors are attempting to offer the whole apple. And they are spending huge sums of money in the process.<p>But most businesses don't really care about most of the apple --- they only need their special bite out of it.<p>For example, doctors mainly care about medicine. Nvidia is attempting to provide the hardware needed for local, specialized models.
I think it is likely to appeal to video and photo editors who want to use AI tools (the press release has a quote from Blackmagic Design, as well as from Adobe, who I think have no stomach for their own cloud AI).<p>But I don’t know about specialised: this could run quite large models with MoE.
Performances of local models are pretty bad compared to what AI vendors offer, token generation is just too slow to be that useful. And you need to allocate GBs of memories, something that will stay very expensive to buy for a long time.<p>Running local models will stay niche for a while, unless we see breakthroughs
cant wait til someone figures how to run Linux on one of these
Intel's basic architecture keeps accelerators away from main system memory, unlike, for example, IBM's POWER architecture where the CPU and GPU are equal 'users' of memory. It's not a great breakthrough to suggest something different. The problem is - it's different, and not compatible with a lot, or most, or all, existing hardware. Also, there are some security concerns, as @stego-tech noted.
And it will be expensive - right?<p>Nvidia is milking the market now. We need more competition again - currently we have a mafia control the prices, not just Nvidia but all the AI companies. The price increases should be paid for them, not by us. "Free market" is being manipulated by them here.
Does this person know that this is the same GB chip in the DGX Spark? It isn't some proposed thing, it's a chip loads of people have on their desk right now, and there are endless benchmarks of it.<p>Decent single core (a long ways from Apple level, but decent), but it makes up for it in cores to provide M5 level performance, CPU wise. Memory bandwidth it is kind of starved, at 1/6th many GPUs.<p>They got Microsoft to customize Windows for the RTX Spark, and will likely have to <i>brutally</i> throttle it when running as a laptop (it's literally a 140W TDP chip), and that's neat. It's going to be a very expensive laptop.
This is probably the better way to frame it: not "Nvidia is proposing a new CPU system" but "Nvidia is trying to move an existing GB/Spark-class platform into a Windows PC form factor"
I heard the memory bandwidth is not just slower than on a GPU, as expected, but is significantly slower than Apple’s unified memory.
Plus John Carmack has reviewed it, he was not amazed.
"Major banana producer suggests shifting more ice cream store menus to banana splits, and increasing the amount of bananas per serving"
[dead]
> I am not sure how many people will run AI models locally. It still seems like a niche application to me.<p>Bill Gates had a quote some years ago...<p>People have still not learned how fast we improve our tech and how much cheaper thing gets I guess :)
Memory isn’t getting cheap soon, and you need a lot of it for local models
We had a thing called globalism that drastically reduced costs. Globalism right now is on life support. Given geopolitics, I don’t see how it’s going to survive.
"I am not sure how many people will run AI models locally. It still seems like a niche application to me."<p>Clip me :). You are currently living through the final stages of unrestricted computing in the hands of the 'public'. Our regimes are going to pull up the drawbridge in the name of 'safety'. Download the open models asap and prepare for an airgapped computing environment. That will be <i>your</i> frontier in not extremely neutered AI in the near future.<p>I am so hoping I'm completely wrong on this btw.