MacBook M5 Max vs Razer Blade 18 RTX 5090: Which Wins for Devs?
M5 Max MacBook vs Razer Blade 18 RTX 5090 compared on Geekbench, SSD speed, and .NET compile times to see which laptop actually wins.
How does the M5 Max MacBook compare to the Razer Blade 18 with RTX 5090?
In direct benchmark testing, the M5 Max MacBook consistently beat the Razer Blade 18 with RTX 5090 across CPU, browser, and compilation workloads, even against the Razer running plugged in on a custom high-performance power plan. The Mac posted higher Geekbench scores, faster JavaScript engine tests, and roughly two times faster .NET build times. The one area where the Razer pulled ahead was random-access SSD performance, which matters for compiled code and disk-heavy builds.
TL;DR
- Geekbench 7 scores favored the Mac by a wide margin, with the M5 Max hitting 3,756 single-core and 35,623 multi-core versus the Razer’s best result of 2,918 single-core and 24,149 multi-core, even after the Razer was switched to a custom high-performance power plan.
- Power settings make a huge difference on the Razer, since running it unplugged in balanced mode produced dramatically lower scores (1,840 single-core, 15,118 multi-core) than running it plugged in on a high-performance plan.
- Browser and JavaScript benchmarks were closer but still Mac-favored, with Speedometer landing at 63.5 on the Mac versus 48.3 on the Razer, and the V8 team’s web tooling benchmark showing a geometric mean of 41.9 versus 35.99.
- Raw Python number-crunching was nearly tied, with a Mandelbrot algorithm test finishing in 11.3 seconds on the Mac and 13.5 seconds on the Razer despite the Razer having 24 CPU cores versus the Mac’s 18.
- .NET compilation times clearly favored the Mac, with a large test project (100,000 classes and namespaces) cold-building in 45 seconds on the Mac versus 56 seconds on the Razer, and warm builds nearly twice as fast on the Mac.
- SSD performance was mixed, with the Mac’s Gen 5 drive roughly doubling the Razer’s sequential read and write speeds, but the Razer actually edged out the Mac on random read/write performance, which matters more for compiled code.
- External Thunderbolt 5 drive performance dropped noticeably on the Razer, with write speeds falling to around 1,300 in testing, suggesting its Thunderbolt implementation still needs work despite using an Intel platform built for it.
- ✕a coding agent
- ✕no-code
- ✕vibe coding
- ✕a faster Cursor
The one that tells the coding agents what to build.
What changed in this year’s hardware?
The Razer Blade 18 moved from an RTX 4090 to an RTX 5090, bumped VRAM from 16GB to 24GB, and switched to a new Intel Core Ultra 9 processor. On paper, that’s a meaningful jump. The MacBook side moved to the M5 Max, Apple’s latest high-end chip, which also brought a generational SSD upgrade to Gen 5 NVMe drives, doubling sequential read and write speeds compared to the previous generation.
Last year’s comparison between these two product lines wasn’t close, with even a mid-tier M4 Pro chip beating the Razer’s previous configuration. The core question this year was whether the new components closed that gap. The updated Razer runs noticeably quieter under load than its predecessor, which had a reputation for aggressive fan noise, and it handled sustained workloads without the same acoustic drama.
Why does power mode matter so much for the Razer?
Windows laptops behave very differently depending on power settings, and the Razer Blade 18 illustrated that clearly. Out of the box, unplugged, and in balanced mode, its Geekbench 7 scores came in at 1,840 single-core and 15,118 multi-core. That’s a steep drop from its potential.
Switching to a high-performance setup, by plugging in the laptop and creating a custom power plan through the command line (using powercfg), pushed the numbers up substantially: 2,918 single-core and 24,149 multi-core. Interestingly, running the same test in Windows’ default balanced mode while plugged in produced nearly identical results (2,908 / 23,957), meaning the real lever isn’t the named power mode but whether the laptop is plugged into the wall at all.
The MacBook doesn’t have this problem. Apple Silicon runs at consistent performance whether plugged in or on battery, when set to high power mode. That’s a meaningful practical difference for anyone who actually works untethered from an outlet, which is the entire point of owning a laptop.
How did the two machines perform on real developer workloads?
Geekbench is a reasonable proxy, but compilation benchmarks get closer to what developers actually experience. Using Damian Edwards’ DevBench repository, which tests .NET builds across a hello world project, a large synthetic project with 100,000 classes and namespaces, and a real CMS project called Orchard, the Mac won every round.
On the large synthetic project, the Mac completed a cold build in 45 seconds and a warm build in 8.9 seconds. The Razer needed 56 seconds for the cold build and 15 seconds for the warm build, roughly double the Mac’s time. On the Orchard CMS project, the Mac finished a cold build in 21.8 seconds versus 42 seconds on the Razer, again about twice as fast, with similar gaps on warm and incremental builds.
Other agents start typing. Remy starts asking.
Scoping, trade-offs, edge cases — the real work. Before a line of code.
Browser-based tests told a similar but tighter story. Speedometer, which simulates real framework workloads in React, Vue, and Angular, and doubles as a stand-in for Electron-based editors like VS Code, Cursor, or Windsurf, scored 63.5 on the Mac against 48.3 on the Razer. That’s still a clear win for the Mac, but 48.3 is a genuinely strong result for a Windows laptop, better than last year’s Razer score of 23.
The V8 team’s web tooling benchmark, which measures JavaScript-heavy tasks like Babel transpilation, TypeScript checking, and minification with no disk I/O involved, showed the Mac ahead across every sub-test: Babel (39.6 vs 34.4 runs per second), CoffeeScript (37.2 vs 26.06), and TypeScript (53.39 vs 47.29). The geometric mean landed at 41.9 for the Mac versus 35.99 for the Razer.
Where does the Razer Blade 18 actually win?
The clearest win for the Razer came down to SSD random read/write performance, the number that correlates most closely with compiled code and everyday disk I/O during builds. Despite the Mac’s Gen 5 drive crushing the Razer on raw sequential speeds (13,769 MB/s read and 13,555 MB/s write on the Mac versus 7,000 read and 6,300 write on the Razer), the Razer posted slightly better random access numbers internally.
That advantage didn’t carry over to external drives. Testing an identical Thunderbolt 5 external SSD (a Samsung 9100, one of the fastest Gen 5 drives available) on both machines showed the Mac’s external performance dropping to around 6,960 MB/s read and 6,600 MB/s write, still respectable. The Razer’s external write speed dropped much further, down to roughly 1,300 MB/s in repeated tests, even when using the correct labeled Thunderbolt 5 port (the Razer’s two USB-C ports aren’t labeled, and only one supports Thunderbolt 5). That points to a weaker Thunderbolt implementation on the Intel-based platform, despite the RTX 5090 and Core Ultra 9 pairing being marketed as high-end.
Raw parallel CPU throughput was close to a wash. A Mandelbrot set calculation in Python, which pegs every available core, finished in 11.3 seconds on the Mac and 13.5 seconds on the Razer, even though the Razer has more physical cores (24 versus the Mac’s 12 performance and 6 efficiency cores). That’s a genuinely competitive result for the Razer and suggests raw multi-threaded throughput isn’t where the Mac’s advantage comes from.
Is the Razer Blade 18 worth it for developers?
For anyone doing serious compilation work, browser-based development, or needing consistent performance on battery, the Mac’s numbers make a stronger case. The Razer’s need for careful power configuration to hit its ceiling, its weaker random SSD and external drive performance, and its slower compile times are real practical downsides for a machine in this price bracket.
Where the Razer still makes sense is gaming and any workload that benefits from a dedicated GPU with 24GB of VRAM, something the Mac cannot match in the same way. For someone who wants a single machine that handles both productivity work and serious gaming, the Razer remains the more versatile choice on the gaming side, even if it trails on pure development benchmarks.
Frequently Asked Questions
Does the RTX 5090 make the Razer Blade 18 faster than the M5 Max MacBook?
No. Despite the upgrade from RTX 4090 to RTX 5090 and more VRAM, the Razer Blade 18 lost to the M5 Max MacBook on Geekbench, browser benchmarks, and .NET compilation tests. The GPU upgrade matters most for gaming and GPU-bound workloads, not general CPU-driven development tasks.
Why did the Razer Blade 18 perform so much worse unplugged?
Windows laptops often throttle performance significantly on battery to preserve battery life, and the Razer Blade 18 showed a large gap between unplugged balanced mode and plugged-in high-performance mode. The MacBook’s M5 Max doesn’t have this issue and maintains consistent performance regardless of power source.
Is the Mac’s SSD actually faster than the Razer’s?
On sequential read and write speeds, yes, the Mac’s Gen 5 drive is roughly twice as fast. But on random read/write performance, which is more relevant to compiled code, the Razer’s drive performed slightly better internally, even though it fell behind on external Thunderbolt 5 drive performance.
How much faster is the Mac at compiling code?
In .NET build tests using real and synthetic projects, the Mac completed cold builds and warm builds in roughly half the time of the Razer Blade 18. A large synthetic project with 100,000 classes built in 45 seconds cold on the Mac versus 56 seconds on the Razer, with a bigger gap on warm builds (8.9 seconds vs 15 seconds).
Should developers buy the Razer Blade 18 or the M5 Max MacBook?
It depends on the use case. The M5 Max wins on raw development benchmarks, consistent battery performance, and compile times. The Razer Blade 18 remains a stronger choice for gaming and GPU-intensive workloads that benefit from the RTX 5090’s VRAM and CUDA support, which macOS cannot replicate.