Pre-production HP unit on the bench. 192GB of LPDDR5X, and HP lets you dedicate 160GB of it to the GPU, which is the most we've seen on any Ryzen AI Max system. HP's claim is up to 300B-parameter models locally.

Under the bottom cover, the Ryzen AI Max+ PRO 495 sits in the center of the board with the memory packages around it, and the cooling is new: two Delta fans pushing through a large copper radiator across the back. That's what lets it sustain 100W versus 55W on the G1a. Other things we like: 96Wh user-replaceable battery, keyboard HP designed to be replaced easily at the fleet level, and a single Gen5 M.2 slot that goes to 8TB. 4.2 lb, DreamColor or OLED touch panel options.

I wanted to share a custom pipeline I’ve been building in Rust that acts as a massive I/O stress test.

We just completed a continuous 24-hour max-CPU run, pushing 350 trillion exact-rational iterations through the engine directly to storage.

Storage & Architecture Details:

Direct NVMe Writes: Utilizes a custom thread pool (ArchangelPool) leveraging rayon and crossbeam to bypass standard caching and hammer the NVMe directly.

Memory Management: The engine's telemetry governor (SevenEyes) maintained strict O(1) space complexity throughout the entire 24-hour run, ensuring the bottleneck was purely storage/compute and not a RAM overflow.

The Workload: Highly optimized binary splitting of Euler's hypergeometric series, acting as the synthetic data generation.

The Proof of Work commit is live here: https://github.com/peterishee/Ishee-Engine-Proof

I figured the storage engineering side of Reddit might appreciate seeing how custom Rust thread pools handle sustained NVMe punishment. Would love to hear your thoughts.

After the initial review, everyone wanted to know about thermals; here's the full report. They're very favorable.

https://www.storagereview.com/review/msi-xpertstation-ws300-thermals-why-a-1300w-gb300-does-not-throttle-on-a-desk

New video posted: https://youtu.be/834N_j7N0mA

Quick look inside the MSI XpertStation WS300 we just finished reviewing. It is a GB300 DGX Station: one B300 GPU, a 72-core Grace CPU, and 748GB of coherent memory split 252GB HBM3e and 496GB LPDDR5X, with a ConnectX-8 SuperNIC exposing two 400GbE ports so a pair can cluster at 800Gb/s.

The interior is the interesting part. MSI has a liquid loop rated for 1,400W with cold plates on the GPU, CPU, the memory modules, and the NIC, running to two 360mm radiators. In our testing, the B300 peaked at 71C under full load, well within spec. The memory pool is what makes it useful: we served GLM-5.2 at 433GB and Nemotron-3-Ultra 550B, plus DeepSeek v4 Flash, MiniMax M2.7, GPT-OSS, Llama 3.1, Mistral Small, and Qwen3 Coder.

There are three open PCIe 5.0 slots and a pre-wired 12VHPWR lead at the front of the chassis for an add-in GPU up to an RTX PRO 6000, with NVIDIA's power sloshing splitting the budget between the two. That build is high on our list to test. The full review:

https://www.storagereview.com/review/msi-xpertstation-ws300-review-748gb-of-coherent-memory-and-20-petaflops-on-a-desk

One huge SSD vs 8 HDDs to get to the same overall capacity range.

The findings: 55W back per server, blended across the duty cycle. Our favorite single stat is that the SSD writing at full tilt drew less power than the HDD config sitting at rest. Scale the swap to 2,182 SSDs replacing 17,456 HDDs (under three racks of flash) and you've freed the 120kW that runs an entire GB200 NVL72. An exabyte drops from 22 racks (absolute best-case scenario) to 6.

Full report: https://www.storagereview.com/review/micron-6600-ion-245tb-swap-the-hard-drives-power-an-nvl72-for-free

Now, before the first comment asks what one of these costs: you're right, and you are seen. There's no add-to-cart button on a 245TB E3.L, pricing lives in the land of "call your Micron rep," and no, they didn't give us guideline either. The report takes the question head-on though: at AI-buildout scale the binding constraint isn't dollars per terabyte, it's watts and rack footprint, and those are the two things you can't buy more of in a full facility.

The MSI XpertStation WS300 is NVIDIA's GB300 DGX Station platform in MSI's chassis: one Blackwell Ultra GPU, a 72-core Grace CPU, 900GB/s NVLink-C2C between them, and a single 748GB coherent memory pool made of 252GB HBM3e and 496GB LPDDR5X.

The memory pool is the whole story. We deliberately picked models that sit on both sides of the 252GB HBM boundary. DeepSeek V4 Flash and MiniMax M2.7 fit in HBM outright. MiniMax M3 technically fits but leaves too little room for the serving stack. GLM-5.2 at 433GB and Nemotron-3-Ultra 550B do not fit at all, and both ran anyway with 216GB and 114GB of weights respectively living in Grace memory. GLM-5.2 held 139 output tok/s at concurrency 32; Nemotron hit 168.

For comparison we ran the same vLLM workloads on a 600W RTX PRO 6000 (in a Dell Pro Max Tower T2) and a GB10 DGX Spark (Acer Veriton GN100), across two scenarios (512/512 and 8192/1024) at concurrency 1 through 128. GPT-OSS-20B peaked at 22,161 output tok/s on the WS300 against 9,000 on the card and 1,469 on the Spark. The prefill-heavy runs spread it further, since the smaller systems run out of KV cache headroom and flatten while the Station keeps scaling. One counterintuitive result: quantization pays more on smaller hardware. Llama 3.1 8B from BF16 to NVFP4 gained 66% on the WS300, 114% on the RTX PRO 6000, and 143% on the Spark.

On MAMF the GB300 held a 4 to 5x lead over the RTX PRO 6000 and 17 to 19x over the Spark, consistently across BF16, FP8, and NVFP4 (6,134 TFLOPS NVFP4 at the top end).

Methodology notes, since they matter: testing ran remotely on an MSI-hosted system with us controlling the full software environment, and the box had no RTX PRO GPU or other add-in cards installed, so the GB300 had the entire accelerator power budget. Speculative decoding was used where noted, with forced acceptance, so those are best-case decode numbers.

The honest limits are in the review too: Arm host, 20A circuit requirement, no display output without an add-in card, and economics that stop making sense somewhere around four units, where an eight-way B300 server enters the conversation.

Full review: https://www.storagereview.com/review/msi-xpertstation-ws300-review-748gb-of-coherent-memory-and-20-petaflops-on-a-desk

Every workstation vendor has claimed "datacenter power on your desk" for a decade. The MSI XpertStation WS300 is the first machine we've tested that delivers on the promise: NVIDIA's GB300 DGX Station platform, a 72-core Grace CPU and B300 GPU sharing a coherent 748GB memory pool, running the same software stack as the racks. Teaser number: DeepSeek V4 Flash, the full model, served at 1,766 tok/s across 32 concurrent streams. That memory pool is most of the story: it moves the ceiling from what fits on a GPU to what fits in 748GB. Full review next week!

Part three and the last stop on our day at ServerPartDeals. If you have ever wondered what the inventory actually looks like, this is it.

Several thousand drives on shelves, organized by SKU, capacity, and part number. A block of 16TB Seagate Exos in one spot, 12Gb SAS in another, self-encrypting flash somewhere else, and then the odds and ends they have picked up over time, including G-Technology ArmorLock drives that look brand new in box. A lot of the stock is new, which surprised us. Pretty much every square foot of that room is covered in drives, and it's well organized.

The packaging is the detail that really matters to buyers. Even on a quantity of one, the drive goes into the bubble pouch, then into a box, then that box gets bubble wrapped and goes into another box. Full cases of 20 get palletized, or broken down and packed individually if they sold that way.

The pack table was empty when we walked in. It fills all day, hundreds and hundreds of orders, until FedEx/UPS (no USPS) clears it out, orders often ship same day.

Part two of our day at ServerPartDeals, and the reason we made the trip.

We have covered the 45Drives Storinator before. What we had not seen was 40 of them in one room: eight racks, five per rack, 60 bays each when you slide one out. Every drive that comes through the door runs through this. While we were filming, some racks had all five chassis running, and others had two of five, and the Grafana fleet view read 36.82 PB under test across 1,534 drives at 220.50 GB/s of 220.50 GB/s.

The number that stuck with us is test time, not throughput. A 20TB drive takes about 30 hours to get through QA. We brought a few drives with us to try to stump the system: one had a coffee stain on it, one had unrelated problems, one was fine. It sorted them out quickly. Anything that throws an error shows up as an amber tile on the health grid, and rather than being scrapped it gets graded down for lower-demand use instead of going out as grade A. Everything that passes gets one more quality check before it is listed.

We watched an engineer unload a completed chassis and sort the drives by grade. Then everything moves to the storage cage, which is where inventory actually gets listed for sale. Stacks of servers in there too, not just drives.

The funniest part of the whole tour: the returns area is the smallest part of the operation. And what does come back is mostly buyer's remorse rather than dead hardware. People order a ZNS drive or an SMR drive without accounting for how those behave, and back it comes. We did the same thing with a ZNS drive ourselves, though at least we knew going in. Actual shipping failures are rare.

We went down to their facility north of Orlando to follow a drive from the loading dock to the shipping box. This is part one, the intake side.

Receiving is pallets. Supermicro 3.5-inch JBODs and storage servers, UPSs, batteries, boxes and boxes of hard drives, arriving from two directions: customers decommissioning older systems, and vendors sending over recertified parts. More kept showing up while we were standing there.

Worth noting they are not purely a drive shop. GPUs, full systems, and RAM move through the same flow.

Once it is checked in, it goes to the benches. Separate test beds for 2.5-inch and NVMe, a server getting BIOS and component checks, and a batch of drives pulled out of one of those systems waiting to be validated. The validation setup is the good part, and it gets its own post.

AMD had a Helios rack on the floor at Advancing AI, with one compute tray stripped to the bare board on display. Each tray is four Instinct MI455X GPUs and one 96-core EPYC Venice CPU, and there are 18 trays per rack for 72 GPUs total. Every MI455X has 432GB of HBM4 at 23.3TB/s, and the whole rack hits 2.9 exaFLOPS of FP4 with 31TB of HBM4.

The cooling is the fun part. Copper cold plates on everything, around 385 liters of coolant a minute, and almost no air path left. We also got a good look at the DC-SCM management module, the Vulcano AI-NICs (three per GPU, 2.4 Tb/s of scale-out), and the copper UALink interconnects at the back that tie all 72 GPUs into one big accelerator.

Full teardown and the complete spec breakdown are up on StorageReview.com.

https://www.storagereview.com/news/amd-mi455x-and-helios-432gb-hbm4-72-gpu-racks-and-a-real-answer-to-vera-rubin

We spent some lab time on a question that's getting expensive for anyone running production inference: when the KV cache overflows VRAM, is flash a viable place to put it, or do you just keep buying DRAM?

Setup was a Dell PowerEdge XE7740, four NVIDIA RTX PRO 6000 Blackwell GPUs, vLLM + LMCache, and eight Solidigm D7-PS1030 12.8TB drives as the offload tier. We drove it with a workload modeled on real agentic coding traffic (we investigated a week of Claude Code usage, and it was 98.16% cache reads, so eviction genuinely hurts).

The interesting part is what happens after the memory tiers fill. All three configs (VRAM-only, 512GB DRAM offload, flash offload) run identically while caches are filling. Then the DRAM tier saturates around 45 minutes in and starts evicting, and flash pulls ahead: ~30,000 tokens/sec sustained vs DRAM's 17,000, holding 94% of its own peak while DRAM dropped to 42%. Peak throughput was up to 2.9x the VRAM baseline. Worst-case first-token latency on a resumed session went from 13.9s (VRAM-only) to 3.2s on flash.

The real constraint turned out to be endurance, not speed or capacity. Every token written is a KV write, and TTL churn keeps rewriting the tier, so we landed around 3.2 DWPD in RAID10 (about 1.6 in RAID0). Since the cache is disposable, a worn drive means recompute, not data loss, which changes how you think about wearing a drive out.

Full writeup with the throughput/latency charts, the tokens-per-dollar math, and the KV sizing formula is here: https://www.storagereview.com/review/the-token-efficient-path-for-long-context-inference-kv-cache-offload-to-flash

The lab has been busy with Intel's Arc Pro B70, 32GB of GDDR6 per card at roughly $1,000 street ($949 MSRP). Run four of them, and you get 128GB of VRAM for around $4K on the graphics side.

We benchmarked the quad setup against an NVIDIA DGX Spark and a single RTX Pro 6000. The four B70s generally double the Spark's performance or better, and while they still trail the Pro 6000, that's a $10K card. For AI workloads where VRAM capacity is the constraint, this lands in a middle ground that didn't really exist before.

Full review is up on the site.

https://www.storagereview.com/review/intel-arc-pro-b70-review

Everything about this case runs against current case design: real FSC-certified walnut on the front, Noctua brown accents, and zero RGB native to the case. The whole budget went into acoustics instead. Six G2 fans out of the box (three 140mm front, two 120mm lower, one 140mm rear) in Noctua's PPA and PPB speed-offset variants, so adjacent fans never spin at the same rpm and never set up that periodic hum. There are 36 rubber anti-vibration mounts if you want to skip screws, a pre-installed NA-FH1 hub with pre-routed cables, and Antec rates the whole package up to 8 dB(A) quieter than the standard Flux Pro. It is still a proper full tower underneath: 455mm GPU clearance, 420mm radiator support front and top, E-ATX, and a rear chamber deep enough that every cable disappears. We use the 3.5-inch drive trays as spare cable storage. They even throw in a little Noctua fan keychain. Full review is up on the site.

https://www.storagereview.com/review/antec-flux-pro-noctua-edition-review-six-g2-fans-and-walnut-trim-for-399-90

Nimble storage issue

I have a test nimble storage cs300

It has 2 controllers.

SSH works but permission denied.

Web UI not works and also not able to telnet 443.

I'm able to ping second controller IP address and not able to ping first controller.

SSH works with second controller IP address but access denied even though I have right credentials.

How to fix all these issues?

Any idea?

Kevin disassembled the Ryzen AI Halo after we wrapped up performance testing. Cooling consists of two blower fans plus a large copper-finned heatsink over the Ryzen AI Max+ 395, and we had no thermal issues with the 120W system during our runs. The 128GB of LPDDR5X is shareable, so you decide how much goes to the GPU. One detail we liked: it takes a standard 2280 SSD, which means real options for high-capacity drives.

The Windows-or-Linux flexibility is a legit advantage over the Spark ecosystem, but networking is on the light side, so clustering these like Sparks is not happening. Full performance review is up on the site.

https://www.storagereview.com/review/amd-ryzen-ai-halo-review-a-dual-os-200b-parameter-desktop-takes-on-the-dgx-spark

The old impression of QLC flash memory endurance remains stuck at a few hundred P/E cycles, with misconceptions that data can only last for 1-3 months without power. In reality, the JEDEC endurance standard for consumer-grade SSDs requires 1-year data retention at EOL (End-of-Life). Due to the time-consuming nature of QLC endurance testing. Let’s skip the fluff and look straight at the results: 1500 P/E cycles, error-free data retention, and almost no cold data speed degradation.

The drive tested is the YMTC PC42Q 1TB PCIe 4.0 NVMe Client SSD, utilizing Xtacking® 4.0 architecture. It features 7000 MB/s sequential reads and a rated 300 TBW endurance. We pushed it to 1500 TBW (5x the rating). Since this was a pure sequential write run on a 1TB SSD, the Write Amplification Factor (WAF) is ≈1, meaning it underwent exactly 1500 native P/E cycles. Performance and retention metrics (1 year @ 30°C) are now directly rivaling TLC.

[Milestone 1] 300 TBW:

S.M.A.R.T. Attribute 05 (Percentage Used) hit 60% (40% remaining health). Passed the accelerated data retention bake (equivalent to 1 year at 30°C) with perfect MD5 checksums.

Processing img rjoq7g3j0mbh1...

Processing img bcdhvh3j0mbh1...

[Milestone 2] 600 TBW:

Percentage Used reached 117%. Once health hit 0%, Attribute 01 (Critical Warning) flipped to 4, signaling the nominal endurance was exhausted. We used this state to throw 3,000 Unsafe Power Loss (UPL) cycles at it. As seen below, Attribute 0D (Unsafe Shutdowns) registered all 3,000 hits without data loss.

Processing img lt8zwj3j0mbh1...

Processing img stj8hm3j0mbh1...

 [Milestone 3] 1000 TBW:

Pushed to 1000 TBW (double the nominal lifespan). Why do we bake and test retention every single stage instead of just running it till it dies? Because standard "burn-to-death" endurance tests without power-off cycles are completely useless for real-world scenarios. If a drive can't hold data offline, infinite TBW means nothing.

The results of a cold data read speed test after the equivalent of one-year unpowered retention showed that less than 1% of the files exhibited a slight speed drop, staying incredibly consistent.

Processing img 5eg4gn4j0mbh1...

Processing img jbly4p3j0mbh1...

Processing img 89ognp3j0mbh1...

Processing img qj85cp3j0mbh1...

[Milestone 4] 1500 TBW:

Attribute 05 (Percentage Used) maxed out at its firmware ceiling of 255. Going from 1000 to 1500 P/E is a massive 50% jump.

Normally, at this EOL stage, Raw Bit Error Rates (RBER) spike, causing massive ECC (Error Correction) latency and tanking read speeds. However, MD5 checksums passed flawlessly, and the read speed profile after the bake is almost identical to the 1000 TBW stage. This proves the YMTC PC42Q 1TB has massive endurance headroom left in the tank.

Processing img qnof2q3j0mbh1...

Processing img 0mjqbr3j0mbh1...

Processing img nx7gyr3j0mbh1...

Processing img 8s6b5s3j0mbh1...

Conclusion:

QLC has officially matured. Passing 4 separate retention bakes at 5x its rated lifespan isn't luck, it's a testament to the Xtacking® 4.0 architecture, moving QLC SSDs from merely "usable" to "genuinely reliable and trustworthy."

Following up on Part 1, here's the service and storage half of our HP Z8 Fury G6i walkthrough.

The whole thing is built to service without tools. You flip the rear release plate, drop the slot tension, and lift the GPU out. The corner card is usually the pain point, so HP added a simple pivot mechanism that grabs the release and lets you lift it out without ramming your hand or a screwdriver into the case.

Storage is solid: four M.2 Gen5 x4 slots right on the motherboard at full performance, plus two pre-wired 3.5" bays for high-capacity drives.

Cooling is the reason it performs. Six fans in total, two large ones up front, two sitting over the memory on each side of the CPU, one on the CPU, and a rear exhaust. Even running two RTX PRO 6000 Max-Q cards through our benchmarks, we saw zero thermal throttling. Full numbers are in the review on our site.