Flash memory is simultaneously shrinking and expanding. The actual memory cells are getting smaller thanks to advancements in fabrication technology, fueling an increase in density that enables higher-capacity chips. For the most part, that’s just great. Higher bit densities reduce the cost per gigabyte, while higher-capacity chips facilitate SSDs with more total storage.
Unfortunately, stuffing more gigabytes into each chip also presents a problem. SSDs now require fewer chips to hit the same capacity, and in some cases, they don’t have enough NAND components to fully exploit the parallelism in modern controllers. That’s why smaller SSDs typically have lower write performance ratings than larger ones.
Multiple SSDs use high-speed caches to make up for slower write performance, but none are quite as ambitious as Micron’s new M600. The memory giant’s latest contender can toggle any part of its NAND between SLC and MLC modes, allowing it to tap unused area as a dynamic SLC cache. Micron claims this cache delivers a nice performance boost at lower capacities, and we’ve tested the 256GB version against the 1TB flagship and dozens of other SSDs to see how well the scheme works.
We’ve also taken a mini M.2 variant for a spin to see how it stacks up. There’s much to discuss, so let’s get started.
A familiar cocktail with a twist
The M600’s hardware components are similar to those in the Crucial MX100, which is sold by Micron’s consumer brand. Both drives combine the company’s homegrown 16-nm flash with an off-the-shelf Marvell controller.
Although Crucial used to mirror Micron’s offerings, the MX100 marked the beginning of a divergence. Having identical lineups created too much confusion and pricing overlap, Micron told us, so the two brands will do their own thing moving forward. They’ll continue to pull from the same internal technology portfolio—and Crucial will still target consumers while Micron focuses on businesses, system builders, and PC makers—but their drives will be different.
Micron’s 16-nm NAND can switch between SLC and MLC modes on the fly. The MX100 doesn’t take advantage of this capability, but in the M600, custom firmware manages the transitions at the block level. The caching scheme, dubbed Dynamic Write Acceleration, houses incoming data in SLC blocks before moving the data to MLC storage during idle periods.
SLC NAND has higher writes speeds because the programming process is much simpler with only one bit per cell. However, SLC also has less storage capacity than two-bit MLC NAND, reducing the M600’s effective cache size to half its MLC capacity. This discrepancy poses a problem for sustained writes that leave no idle time to transfer data from SLC to MLC blocks. The M600’s solution is to switch to MLC writes as the NAND approaches saturation. If writes continue unabated, the M600 eventually starts transferring previously cached data to main storage while continuing to write fresh data from the host.
As one might expect, this juggling act has performance implications. The graph below shows how the M600 256GB’s sequential write speed changes as the drive fills up in an HD Tune test.
The M600 enjoys the higher write speed of SLC NAND up to 46% of its total capacity. Performance drops considerably in the stretch from 46-58%, when writes continue in MLC mode. After that, the drive has to perform SLC-to-MLC transfers while continuing to write incoming data. This multitasking plunges the sequential write speed below 100MB/s and into mechanical storage territory.
Obviously, Dynamic Write Acceleration isn’t ideal for sustained workloads. The scheme is meant to accelerate the short bursts of write activity found in typical client workloads.
There’s another potential fly in the ointment, though. Any cached data that makes its way to MLC storage will be written twice, eating into the NAND’s limited endurance. Fortunately, SLC writes are less damaging than MLC ones. Micron has also adjusted “proprietary NAND trims” to offset the endurance penalty associated with write caching. These top-secret settings are “configured during the NAND fabrication process,” and they can be “tuned for different performance and endurance characteristics.” Despite the name, they’re unrelated to the TRIM command used by the operating system to identify deleted data.
Tweaking NAND trims is apparently quite effective, because the M600 has the most impressive endurance ratings we’ve seen in a client-oriented SSD. Micron’s other drives in this category are specced for 72TB of total writes, and so are their Crucial cousins. But the M600 starts at 100TB for the 128GB version, and the endurance rating scales up with the capacity, taking advantage of the fact that larger drives have more flash to burn. The 1TB monster is good for 400TB of total writes, which works out to a staggering 374GB per day for the length of the three-year warranty.
|Capacity||Die config||Max sequential (MB/s)||Max 4KB random (IOps)||Endurance
|128GB||8 x 16GB||560||400||90,000||88,000||100|
|256GB||16 x 16GB||560||510||100,000||88,000||200|
|512GB||32 x 16GB||560||510||100,000||88,000||300|
|1TB||64 x 16GB||560||510||100,000||88,000||400|
Surprisingly, the 1TB and 512GB variants don’t have Dynamic Write Acceleration. Those drives are already fast enough for the controller, according to Micron, and the math works out. The Marvell chip can address up to four chips on each of its eight memory channels, making 32-die configurations ideal for peak performance. At 16GB per die, the cut-off point is 512GB.
Despite falling short of that threshold, the 256GB variant matches the performance specifications of its larger siblings. The 128GB version is a little slower, according to the official figures, but not nearly as much as one would expect given the die count.
In a moment, we’ll see how the M600 256GB and 1TB compare in a wide variety of tests. There are a few loose ends to tie up before that, including encryption support, which is particularly important to Micron’s corporate clients. The M600 supports all the right standards: TCG Opal 2.0, IEEE 1667, and Microsoft eDrive. Even if the 256-bit AES encryption doesn’t keep the NSA out of your business, it should at least prevent thieves and opportunists from snooping.
To protect against data loss due to flash failures, the M600 employs a RAID-like redundancy scheme called RAIN. It also has a measure of power-loss protection. These aren’t must-have features for a lot of enthusiasts, but they provide some peace of mind, and they should appeal to business customers. Noticing a theme yet?
The M600’s high endurance ratings are likely to attract folks who write a lot of data, making health monitoring especially important. Unfortunately, Micron doesn’t offer an easy-to-use Windows app with health information and other drive-related functionality. At least the SMART attributes are loaded with tickers for lifetime remaining, host writes, reserve blocks, reallocated sectors, and various error types. Anyone who wants to monitor drive health with third-party disk utilities can easily tap into those attributes.
And then there are the miniature M600s…
A moment with M.2
The M600 family combines a full line of 2.5″ drives with a collection of tiny mSATA and M.2 units. All the mSATA flavors have the same footprint, but the M.2s are available in single-sided 2280 and double-sided 2260 variants of the form factor. Those numbers refer to the width (22 mm) and the length (either 60 or 80 mm) of the “gumstick” circuit board. Here’s how the M.2 2280 version of the M600 256GB compares to its 2.5″ counterpart:
Awww, isn’t it cute?
The mini versions of the M600 are basically the same as the 2.5″ drives. However, they only scale up to 512GB, and they all have Dynamic Write Acceleration. According to Micron, SLC caching can convey power efficiency benefits by speeding the write process, allowing the drive to return to a low-power state more quickly. Since the mSATA and M.2 models are mostly meant for notebooks, they all have the feature enabled.
DevSleep support is a pre-requisite for SSDs targeting modern notebooks, so it’s no surprise that the M600 supports the ultra-low-power state. The drive also has a built-in throttling mechanism that dials back performance if thermals exceed acceptable limits. Pretty standard stuff.
Despite its fancy form factor, the M600 M.2 uses the same old Serial ATA interface as the rest of the family. It requires an M.2 slot with SATA connectivity, so it won’t work with the PCIe-only M.2 implementations on some motherboards. That SATA requirement also precludes the M.2 drive from working in PCIe adapter cards.
Our storage test systems are too old to have M.2 slots, so we couldn’t throw the mini M600 256GB into the ring with the rest of the SSDs. We did, however, run a few quick tests on the drive and its 2.5″ twin using a newer Gigabyte X99-UD4 motherboard. We also ran the same tests on a handful of comparable Crucial SSDs. All of those drives use slight variations of the same Marvell controller paired with different flash configurations. The M500 and MX100 both employ 16 x 16GB NAND dies, while the M500 has a 32 x 8GB array.
The M.2 and 2.5″ versions of M600 256GB shadow each other in these tests. Although the M.2 is technically faster in a few instances, it’s only ahead by a smidgen.
Impressively, the M600 keeps up with the M550, which has twice as many NAND dies. The M500 and MX100 lag behind, and they’re particularly slow in the sequential write speed test. Dynamic Write Acceleration is evidently quite effective in CrystalDiskMark. Let’s bust out our usual benchmarks to see how it fares in a broader range of tests—and against a larger collection of competitors.
CrystalDiskMark — transfer rates
TR regulars will notice that we’ve trimmed a few tests from our usual suite of storage results. The drives were all benchmarked in the same way, but we’ve excluded the results for tests that have grown problematic or less relevant over time. This abbreviated format should be a little easier to digest until our next-gen storage suite is ready.
First, we’ll tackle sequential performance with CrystalDiskMark. This test runs on partitioned drives with the benchmark’s default 1GB transfer size and randomized data.
We’ve color-coded the results to make the M600—and some comparable Crucial SSDs—easier to pick out of the fray.
In the read speed test, most of the SSDs bump into the limits of the 6Gbps SATA interface. Even the M600’s middle-of-the-pack performance puts it relatively close to the leaders.
The field spreads out quite a bit more in the write speed test, but the M600 doesn’t miss a step. The 256GB and 1TB versions are both in the upper tier, again just shy of the leaders.
HD Tune — random access times
Next, we’ll turn our attention to random access times. We used HD Tune to measure access times across multiple transfer sizes. SSDs have near-instantaneous seek times, so it’s hard to graph the results on the same scale as mechanical drives. The WD Black and Seagate SSHD will sit out this round to focus our attention on the SSDs.
The M600’s random access times are competitive for the most part. However, the 256GB variant stumbles in the 1MB random write speed test, causing it to tumble to the back of the field. The Crucial M500 240GB and MX100 256GB both have quicker access times in that test despite their lack of SLC caching.
TR FileBench — Real-world copy speeds
FileBench, which was concocted by TR’s resident developer Bruno “morphine” Ferreira, runs through a series of file copy operations using Windows 7’s xcopy command. Using xcopy produces nearly identical copy speeds to dragging and dropping files using the Windows GUI, so our results should be representative of typical real-world performance. We tested using the following five file sets—note the differences in average file sizes and their compressibility. We evaluated the compressibility of each file set by comparing its size before and after being run through 7-Zip’s “ultra” compression scheme.
|Number of files||Average file size||Total size||Compressibility|
The names of most of the file sets are self-explanatory. The Mozilla set is made up of all the files necessary to compile the browser, while the TR set includes years worth of the images, HTML files, and spreadsheets behind my reviews. Those two sets contain much larger numbers of smaller files than the other three. They’re also the most amenable to compression.
To get a sense of how aggressively each SSD reclaims flash pages tagged by the TRIM command, the SSDs are tested in a simulated used state after crunching IOMeter’s workstation access pattern for 30 minutes. The drives are also tested in a factory fresh state, right after a secure erase, to see if there is any discrepancy between the two states. There wasn’t much of one with the M600, so we’re only presenting the used-state scores.
Although the M600 isn’t the fastest SSD in our file copy tests, it fares reasonably well overall. The 256GB and 1TB versions are competitive across all five tests, and they’re very equally matched. The same can’t be said for the old M500, which delivers much faster copy speeds in its 960GB incarnation than in its 240GB one. Dynamic Write Acceleration clearly gives the M600 256GB a boost here.
TR DriveBench 2.0 — Disk-intensive multitasking
DriveBench 2.0 is a trace-based test comprised of nearly two weeks of typical desktop activity peppered with intense multitasking loads. More details on are available on this page of our last major SSD round-up.
We measure DriveBench performance by analyzing service times—the amount of time it takes drives to complete I/O requests. Those results are split into reads and writes.
While the M600 1TB has relatively speedy mean service times for both reads and writes, the 256GB version is way behind according to both metrics. The smaller drive has the slowest mean read service time of any of the SSDs, and its mean write service time actually puts it behind the mechanical drives. The Crucial SSDs follow a similar pattern, but their smaller variants don’t suffer as much as the M600 256GB.
All the SSDs execute the vast majority of DriveBench requests in one millisecond or less—too little time for end users to perceive. We can also sort out the number of service times longer than 100 milliseconds, which is far more interesting data. These extremely long service times make up only a fraction of the overall total, but they’re much more likely to be noticeable.
Dynamic Write Acceleration may not produce competitive mean service times, but it definitely cuts down on the number of extremely slow writes. The difference between the M600 256GB and M500 240GB is a full order of magnitude. Even the M550 256GB, which boasts twice the NAND-level parallelism of its M600 sibling, has five times more writes over 100 milliseconds.
With reads, the M600 256GB crosses the 100-ms threshold more often than some of its Crucial peers, including the MX100. Dynamic Write Acceleration definitely doesn’t improve read performance.
Despite its lack of SLC caching, the M600 1TB logs far fewer painfully slow writes than its M550 counterpart. The two are on more equal footing with reads, though the M600 has a definite edge there, as well.
Our IOMeter workload features a ramping number of concurrent I/O requests. Most desktop systems will only have a few requests in flight at any given time (87% of DriveBench 2.0 requests have a queue depth of four or less). We’ve extended our scaling up to 32 concurrent requests to reach the depth of the Native Command Queuing pipeline associated with the Serial ATA specification. Ramping up the number of requests also gives us a sense of how the drives might perform in more demanding enterprise environments.
We run our IOMeter test using the fully randomized data pattern, which presents a particular challenge for SandForce’s write compression scheme. We’d rather measure SSD performance in this worst-case scenario than using easily compressible data.
There’s too much data to show clearly on a single graph, so we’ve split the results. You can compare the M600’s performance to that of the competition by clicking the buttons below each graph.
Instead of presenting the results of multiple access patterns, we’re concentrating on IOMeter’s database test. This access pattern has a mix of read and write requests, and it’s similar to the file server and workstation tests. The results for these three access patterns are usually pretty similar. We also run IOMeter’s web server access pattern as part of our standard suite of tests, but it’s made up exclusively of read requests, so the results aren’t as applicable to real-world scenarios. Our own web servers log a fair amount of writes, for example.
The M600 follows the same basic trajectory as its Crucial counterparts in IOMeter. I/O throughput only scales up slightly as the load increases, unlike with some of the other SSDs, whose transaction rates ramp up dramatically with the number of concurrent requests. The first few data points are the most relevant for client systems, and the M600 is at least fairly competitive there.
Note that the M600 256GB is a step behind the terabyte model throughout. Our IOMeter tests hammer the drives pretty much continuously for six hours straight, so they’re probably not ripe for Dynamic Write Acceleration.
Before timing a couple of real-world applications, we first have to load the OS. We can measure how long that takes by checking the Windows 7 boot duration using the operating system’s performance-monitoring tools. This is actually the first test in which we’re booting Windows off each drive; up until this point, our testing has been hosted by an OS housed on a separate system drive.
Level load times
Modern games lack built-in timing tests to measure level loads, so we busted out a stopwatch with a couple of titles.
Write caching won’t make Windows or games load faster, but the M600 doesn’t need any help on those fronts. Both capacities are within a second of the leaders in our load time tests. So is pretty much every other SATA SSD.
We’re working on an updated batch of load-time tests for our next-gen storage suite. Shoot me an email if you have any suggestions. (And thanks to those who have already chimed in.)
We tested power consumption under load with IOMeter’s workstation access pattern chewing through 32 concurrent I/O requests. Idle power consumption was probed one minute after processing Windows 7’s idle tasks on an empty desktop.
The M600’s idle power consumption is reasonably low—and pretty much identical for the 256GB and 1TB variants. However, the larger drive pulls 1W more when servicing a barrage of IOMeter requests. The continuous nature of our IOMeter load doesn’t present an opportunity for Dynamic Write Acceleration to improve power efficiency. There’s simply no downtime during which the drive can assume a lower-power state.
That’s it for performance. If you’re curious about the other SSDs in this review or about how we conduct our testing, hit up the methods section on the next page. Otherwise, feel free to skip ahead to the conclusion.
Test notes and methods
Here’s a full rundown of the SSDs we tested, along with their essential characteristics.
|Adata Premier SP610 512GB||Silicon Motion SM2246EN||20-nm Micron sync MLC|
|Adata Premier Pro SP920 512GB||Marvell 88SS9189||20-nm Micron sync MLC|
|Corsair Force Series GT 240GB||SandForce SF-2281||25-nm Intel sync MLC|
|Corsair Neutron 240GB||LAMD LM87800||25-nm Micron sync MLC|
|Corsair Neutron GTX 240GB||LAMD LM87800||26-nm Toshiba Toggle MLC|
|Crucial M500 240GB||Marvell 88SS9187||20-nm Micron sync MLC|
|Crucial M500 480GB||Marvell 88SS9187||20-nm Micron sync MLC|
|Crucial M500 960GB||Marvell 88SS9187||20-nm Micron sync MLC|
|Crucial M550 256GB||Marvell 88SS9189||20-nm Micron sync MLC|
|Crucial M550 512GB||Marvell 88SS9189||20-nm Micron sync MLC|
|Crucial M550 1TB||Marvell 88SS9189||20-nm Micron sync MLC|
|Crucial MX100 256GB||Marvell 88SS9189||16-nm Micron sync MLC|
|Crucial MX100 512GB||Marvell 88SS9189||16-nm Micron sync MLC|
|Intel 335 Series 240GB||SandForce SF-2281||20-nm Intel sync MLC|
|Intel 520 Series 240GB||SandForce SF-2281||25-nm Intel sync MLC|
|Intel 730 Series 480GB||Intel PC29AS21CA0||20-nm Intel sync MLC|
|Intel 730 Series 480GB||Intel PC29AS21CA0||20-nm Intel sync MLC|
|OCZ Vertex 4 256GB||Indilinx Everest 2||25-nm Micron sync MLC|
|OCZ Vertex 450 256GB||Indilinx Barefoot 3 M10||20-nm Micron sync MLC|
|OCZ Vertex 460 240GB||Indilinx Barefoot 3 M10||19-nm Toshiba Toggle MLC|
|OCZ ARC 240GB||Indilinx Barefoot 3 M10||A19-nm Toshiba Toggle MLC|
|Micron M600 256GB||Marvell 88SS9189||16-nm Micron sync MLC|
|Micron M600 1TB||Marvell 88SS9189||16-nm Micron sync MLC|
|SanDisk Extreme II 240GB||Marvell 88SS9187||19-nm SanDisk Toggle SLC/MLC|
|Samsung 840 Series 250GB||Samsung MDX||21-nm Samsung Toggle TLC|
|Samsung 840 EVO 250GB||Samsung MEX||19-nm Samsung Toggle TLC|
|Samsung 840 EVO 500GB||Samsung MEX||19-nm Samsung Toggle TLC|
|Samsung 840 EVO 1TB||Samsung MEX||19-nm Samsung Toggle TLC|
|Samsung 840 Pro 256GB||Samsung MDX||21-nm Samsung Toggle MLC|
|Samsung 850 Pro 512GB||Samsung MEX||32-layer Samsung V-NAND|
|Seagate 600 SSD 240GB||LAMD LM87800||19-nm Toshiba Toggle MLC|
|Seagate Desktop SSHD 2TB||NA||24-nm Toshiba Toggle SLC/MLC|
|WD Caviar Black 1TB||NA||NA|
The solid-state crowd is augmented by a couple of mechanical drives. WD’s Caviar Black 1TB represents the old-school hard drive camp. Seagate’s Desktop SSHD 2TB is along for the ride, as well. The SSHD combines mechanical platters with 8GB of flash cache, but like the Caviar Black, it’s really not a direct competitor to the SSDs. The mechanical and hybrid drives are meant to provide additional context for our SSD results.
If you chose to read this page rather than skipping to the conclusion, you might be interested in a couple more naked circuit board shots. No celebrity iCloud accounts were compromised to obtain these pictures.
We used the following system configuration for testing:
|Processor||Intel Core i5-2500K 3.3GHz|
|CPU cooler||Thermaltake Frio|
|Motherboard||Asus P8P67 Deluxe|
|Platform hub||Intel P67 Express|
|Platform drivers||INF update 18.104.22.1680
|Memory size||8GB (2 DIMMs)|
|Memory type||Corsair Vengeance DDR3 SDRAM at 1333MHz|
|Audio||Realtek ALC892 with 2.62 drivers|
|Graphics||Asus EAH6670/DIS/1GD5 1GB with Catalyst 11.7 drivers|
|Hard drives||Seagate Desktop SSHD 2TB with CC43 firmware
WD Caviar Black 1TB with 05.01D05 firmware
Adata Premier SP610 512GB with N0402C firmware
Adata Premier Pro SP920 512GB with MU01 firmware
Corsair Force Series GT 240GB with 1.3.2 firmware
Corsair Neutron 240GB with M206 firmware
Corsair Neutron GTX 240GB with M206 firmware
Crucial MX100 256GB with MU01 firmware
Crucial MX100 512GB with MU01 firmware
Crucial M500 240GB with MU03 firmware
Crucial M500 480GB with MU03 firmware
Crucial M500 960GB with MU03 firmware
Crucial M550 256GB with MU01 firmware
Crucial M550 1TB with MU01 firmware
Intel 335 Series 240GB with 335s firmware
Intel 520 Series 240GB with 400i firmware
Intel 730 Series 480GB with XXX firmware
OCZ Vector 150 256GB with 1.1 firmware
OCZ Vertex 450 256GB with 1.0 firmware
OCZ Vertex 460 240GB with 1.0 firmware
OCZ ARC 100 240GB with 1.0 firmware
Micron M600 256GB with E100 firmware
Micron M600 1TB with E100 firmware
SanDisk Extreme II 240GB with R1131
Samsung 830 Series 256GB with CXM03B1Q firmware
Samsung 840 Series 250GB with DXT07B0Q firmware
Samsung 840 EVO 250GB with EXT0AB0Q firmware
Samsung 840 EVO 500GB with EXT0AB0Q firmware
Samsung 840 EVO 1TB with EXT0AB0Q firmware
Samsung 840 Pro Series 256GB with DXM04B0Q firmware
Samsung 850 Pro 512GB with EXM01B6Q firmware
Seagate 600 SSD 240GB with B660 firmware
|Power supply||Corsair Professional Series Gold AX650W|
|OS||Windows 7 Ultimate x64|
Thanks to Asus for providing the systems’ motherboards and graphics cards, Intel for the CPUs, Corsair for the memory and PSUs, Thermaltake for the CPU coolers, and Western Digital for the Caviar Black 1TB system drives.
We used the following versions of our test applications:
- Intel IOMeter 1.1.0 RC1
- HD Tune 4.61
- TR DriveBench 1.0
- TR DriveBench 2.0
- TR FileBench 0.2
- Qt SDK 2010.05
- MinGW GCC 4.4.0
- Duke Nukem Forever
- Portal 2
Some further notes on our test methods:
- To ensure consistent and repeatable results, the SSDs were secure-erased before almost every component of our test suite. Some of our tests then put the SSDs into a used state before the workload begins, which better exposes each drive’s long-term performance characteristics. In other tests, like DriveBench and FileBench, we induce a used state before testing. In all cases, the SSDs were in the same state before each test, ensuring an even playing field. The performance of mechanical hard drives is much more consistent between factory fresh and used states, so we skipped wiping the HDDs before each test—mechanical drives take forever to secure erase.
- We run all our tests at least three times and report the median of the results. We’ve found IOMeter performance can fall off with SSDs after the first couple of runs, so we use five runs for solid-state drives and throw out the first two.
- Steps have been taken to ensure that Sandy Bridge’s power-saving features don’t taint any of our results. All of the CPU’s low-power states have been disabled, effectively pegging the 2500K at 3.3GHz. Transitioning in and out of different power states can affect the performance of storage benchmarks, especially when dealing with short burst transfers.
The test systems’ Windows desktop was set at 1280×1024 in 32-bit color at a 75Hz screen refresh rate. Most of the tests and methods we employed are publicly available and reproducible. If you have questions about our methods, hit our forums to talk with us about them.
We’d normally bust out our famous value scatters to summarize the M600’s performance, pricing, and overall value proposition. However, the drive won’t be sold through normal retail channels, and Micron isn’t publishing an official price list. All the company would tell us is that the 1TB version will cost around $450 in single-unit quantities, which is pretty affordable even in the context of aggressively discounted consumer drives.
Although we can’t factor in pricing, we can calculate the overall performance scores for the M600 256GB and 1TB. These scores are based on a subset of the performance data from our full suite, with CrystalDiskMark’s sequential transfer rates substituted for older HD Tune results. (More details about how we calculate overall performance are available here.)
The M600 1TB is slightly ahead of the equivalent M550—and it’s one of the fastest SSDs overall. The 256GB version doesn’t score as well as its larger sibling, but it does outpoint comparable counterparts in the MX100, M500, and M550 families. The fact that the 16-die M600 scores higher overall than the 32-die M550 is a testament to the benefits of Dynamic Write Acceleration. To be fair, though, there are lots of older 240-256GB SSDs with higher overall performance.
As we saw in our individual tests, this particular breed of SLC caching doesn’t excel in all situations. Dynamic Write Acceleration is much better suited to short, bursty transfers than prolonged workloads. It’s also more effective when there’s lots of free capacity to serve as SLC blocks. Those attributes are probably a decent fit for typical corporate clients, who are unlikely to fill their drives or hammer them with sustained I/O. That said, they’re less ideal for power users with overflowing Steam libraries and demanding usage patterns.
Even if it’s not a perfect solution to limited NAND-level parallelism, Dynamic Write Acceleration is clearly effective, and the underlying technology is very slick. It will be interesting to see how on-the-fly switching manifests in future Micron SSDs, including those sold under the Crucial banner. There’s considerable potential for further performance improvements in future drives that ditch the pokey SATA interface for faster PCI Express links.
In the meantime, SLC caching allows the M600 256GB to be more competitive than any 16-die SSD ought to be. The 1TB version is a great all-rounder even without the aid of write caching, and both have industry-leading endurance ratings. They also have everything else one might want in a business-oriented SSD, including robust data protection and encryption support.
All things considered, the M600 delivers an appealing package for not only Micron’s typical customers, but also PC enthusiasts and everyday consumers. It’s a shame the drive won’t be available through traditional e-tail channels. If you manage to find one at a decent price, the M600 is definitely worth considering—especially at higher capacities. Another way around the limitations of 16-die configs is simply to buy a bigger SSD.