Seagate's Momentus XT Reviewed, Finally a Good Hybrid HDDby Anand Lal Shimpi on May 24, 2010 9:31 AM EST
- Posted in
- Momentus XT
- Hybrid Drive
A few years ago it seemed as if Hybrid Hard Drives were the future. Yet after a bunch of announcements and hope today we find ourselves in a world with two distinct markets: HDDs and SSDs. If you're willing to pay the price premium and limit maximum capacity, today's SSDs are very fast and if you choose well, reliable.
For a desktop PC this isn't a tough choice to make. I've been advocating a setup where you have a SSD for your OS + applications and a separate RAID-1 array of 1TB or larger drives for all of your music, movies and photos.
Notebook users don't usually have a ton of drive bays and thus only have room for a single drive. It's not a lost cause though, if your notebook is your only machine you can get away with an internal SSD + external storage whether in the form of a NAS or just something you attach via USB when you're at your desk.
For the very portable users that don't want to lug around another hard drive, or for those who refuse to pay the high dollar per GB rates that SSDs command, there hasn't really been an option other than mechanical storage.
Today Seagate is attempting to change that with its latest Hybrid HDD: the Momentus XT.
More 918 Spyder than Prius
Simply put a Hybrid HDD is a mechanical drive with some NAND flash on it that is automatically used by the drive to store data for quicker access. A hybrid drive really just attempts to do what my setup of two drives (SSD + HDD) does manually: put small, frequently used data on NAND flash and put larger, less frequently used data on platters.
In theory you get the best of both worlds, the overall capacity of a HDD and (most of the time) the performance of an SSD.
Seagate's Momentus XT starts with a standard 7200PM 2.5" Momentus drive and adds a 32MB buffer, the largest on any 2.5" Momentus drive. Seagate then makes it a hybrid by adding a single 4GB SLC (!) NAND chip on the drive's PCB. Connect a controller to manage what goes into the NAND and we're in business.
|Seagate Momentus XT Drive Pricing (MSRP)|
|Seagate Momentus XT||$113||$132||$156|
|Seagate Momentus 7200.4||$55||$55||$85|
|Seagate Momentus 5400.6||$50||$55||$65|
The size of the NAND was a shocker to me when I first heard it. I honestly expected something much larger. In the Momentus XT however, the SLC NAND acts exclusively as a read cache - writes never touch the NAND. The drive looks at access patterns over time (most likely via a history table of LBAs and their frequency of access) and pulls some data into the NAND. If a read request comes in for an LBA that is present in the NAND, it's serviced out of the 4GB chip. If the LBA isn't present in the NAND, the data comes from the platters.
If a read request can be serviced out of the NAND, the drive can be spun down which should save power. In practice it's rare that a sequence of reads can entirely be serviced out of NAND. What usually happens is you get a little bit of data out of the NAND and then the drive has to spin up to give you the rest. This can be a bit annoying because you get a drive spinup event in the middle of a data access rather than just before it.
The data in the NAND remains persistent across power cycles, however not formats or defrags. You still have to defragment the drive, but doing so resets the drive's learning back to zero. Defragmenting less often is the only real solution.
It's not a huge problem because the drive learns pretty quickly. By the second time you do anything the Momentus XT is usually a lot faster at the task assuming Seagate's algorithms pull any of the data you're accessing into its on-board NAND.
The chart below shows a comparison of a Western Digital VelociRaptor 600GB, a SandForce SF-1200 based SSD and the Momentus XT in boot times. I simply timed how long it took to boot into Windows 7 from the point the OS began loading to the time I got a cursor on the desktop. After a completed boot I shut down the machine and tried again.
While the first boot takes pretty long on both hard drives, by the second boot the Momentus XT is already noticeably faster than the VelociRaptor. Seagate appears to focus mostly on small, frequently used files and aggressively pulls them into the NAND.
The chart also illustrates a very important point. The SSD's performance is consistent even compared to the first run, while the Momentus XT needs to run through a workload once before it's optimized. This applies to more than just boot time, application loads or any sort of disk access.
Over a short period of time the Momentus XT should get many of the small files you use regularly into its NAND cache but the drive is best optimized for repeatable usage patterns. If you always use the same few applications in the same way the Momentus XT will work very well. I found that it's not very difficult to get data evicted from the NAND cache if you throw a random set of applications/workloads at the drive.
Why a Read Cache?
I've written a lot about the struggles that SSD controllers must deal with to manage writing and re-writing NAND. It's not surprising that Seagate opted to use the NAND on the Momentus XT as a read-only cache. Seagate controls what data gets written to the NAND, which makes block management much simpler. There's never a situation where the drive doesn't know what it needs to keep track of. And by using SLC instead of MLC NAND, Seagate doesn't even have to worry about aggressive wear leveling either. So it's about simplicity, not the perfect hybrid design.
Seagate claims that the 4GB size offered the best balance of price/performance, but I suspect that with more aggressive caching algorithms Seagate could benefit from a larger cache. With more NAND Seagate could also prefetch data into the cache. And eventually, if there is to be a future for hybrid drives, Seagate will have to enable a NAND write cache.
Once you start caching writes as well then you effectively make the jump into the SSD realm in terms of complexity. The read-only design is pretty simple but until we see Seagate enter the consumer SSD space I doubt we'll see a more aggressive hybrid drive.
Note that you shouldn't expect to get the same performance out of the Momentus XT's single NAND device as you would an SSD. Remember that modern SSDs have anywhere between 4 and 10 channels of NAND accessed in parallel to reach their very high transfer rates. A single NAND device isn't going to end up anywhere near as fast. At best the Momentus XT should be able to read from the cache at 20 - 40MB/s depending on the data being accessed and the type of NAND Seagate is using.
Post Your CommentPlease log in or sign up to comment.
View All Comments
enderwiggin21 - Tuesday, May 25, 2010 - linkAlmost 40% more at idle and ~33% more at load is most definitely "considerably more."
Under 10% and *then* you're into the statistically insignificant category.
svend - Monday, May 24, 2010 - linkWill the NAND still be effective when using the XT with an encrypted partition/filesystem? What affect would encryption have on the performance of the XT?
GullLars - Monday, May 24, 2010 - linkThumbs up to seagate for the sollution, the one used in previous hybrids that relied on the OS was not very effective.
I actually made a thread on XS forum a couple of months back discussing a sollution like this, a HDD with a NAND read-only cache using LBA read pattern mapping as caching algorithm.
In my discussion, i suggested using 8-16GB (1-2 dual plane dies) MLC ONFI 2.x NAND on a single channel for lower complexity. This would give up to about 7500 4KB random read IOPS (30MB/s), and 90-180MB/s sequential read (for cache hits). At a cost of roughly 2-3$/GB + a NAND controller, the added price tag would be around 25-50$.
I think this could be interresting for higher capacity 3,5" "black" drives as well as high-performance high capacity notebook HDDs.
auhgnist - Monday, May 24, 2010 - linkHybrid HD seems similar to Intel Turbo Boost technology, in terms of both SSD capacity and NAND type, except that Turbo Boost allows certain level of control such as caching only data accessed some pre-given programs. Any idea how these two compare in terms of performance?
joshv - Monday, May 24, 2010 - linkI mean seriously. Add another 4GB of RAM and let the OS do the caching. Sure, it won't help with boot, but for everything else it should be a lot faster than some SLC NAND on the HD.
enderwiggin21 - Tuesday, May 25, 2010 - linkOr how about both?
mpx999 - Monday, May 24, 2010 - linkIt would be interesting to compare performance of hybrid SSD with software-based flash read cache schemes. There are basically two of them for Windows: built-in Readyboost and third-party eBoostr. Other operating systems have even better mechanisms, eg. Solaris has L2ARC caching scheme for reads and ZIL for writes.
Both Windows caching mechanisms can work with either USB sticks, or memory cards in built-in readers. Second option is very interesting as it means SLC flash cards can be used.
I suspect hardware controlled read-cache as implemented in this hybrid drive will totally beat Windows software -based mechanism in one important application: running virtual machines. It's because hardware cache operates on disk blocks so it doesn't matter it these blocks are from base machine or virtual machine, while software Windows mechanisms rely on file-based statistics, so they only speed up base machine. One would have to create separate cache for each VM to get speedup. Btw. software-based Solaris caching doesn't have this limitation.
vision33r - Monday, May 24, 2010 - linkIt's nowhere need a true SSD in performance and just offers the cheap space of a spindle drive.
The the same has having a SSD internally and carrying a spindle drive externally.
Once SSDs gets cheaper, solution like this will be less interesting.
I expect SSD prices to drop from $99 for a 40GB to like $60, then we'll see 200GB SSD for like $150 or less.
jmv2009 - Monday, May 24, 2010 - linkI don't think writing through the ssd is that important, as it can be effectively cached using the main memory of the system. Only for sustained writes >1 Gb this would become slow if the caching works well.
nsravan - Monday, May 24, 2010 - linkThe site had not much activity since you went on vacation. So I took one too :)