The Benefits of Hybrid Drives

feminazi writes "Flash memory is being integrated with the hard disk by Seagate and Samsung and onto the motherboard by Intel. Potential benefits: faster read/write performance; fewer crashes; improved battery life; faster boot time; lower heat generation; decreased energy-consumption. Vista's ReadyDrive will use the hybrid system first for laptops and probably for desktops down the road. The heat and power issues may also make it attractive in server environments."

Comments

Hybrid Drives!

[Sixtyten]

Will they increase fuel economy as well?

Re:Finally...

[grammar fascist]

This is not a new idea, nor is it new technology... This has been a long time coming.

The prices finally fell to where it's economically feasible.

Personally, I like Intel's idea better (embedding the flash memory in the drive controller), because it should work just fine with existing drives. It might also be upgradeable, but I'm not holding my breath.

Re:another "benefit"

[plasmacutter]

I hate to reply to my own post but look, it's not offtopic.

flash memory is persistant. Unless you provide open apis to allow anyone to develop applications to wipe it, there is no real way to confirm anything that gets stored on it is actually removed.

Every platform, but especially windows, has a history of security exploits, and now the viruses will have somewhere to hide where they will be much harder to dig out, and anyone wanting to implement DRM could build an OS designed to hide critical components of it by burying it on the flash memory.

Re:Old?

[nmb3000]

Windows creates an immense swapfile anyway - why not just get the system to do it on either a designated part of the hard drive, or on a USB 2.0 flash drive?

Actually, has anyone tried that? I expect you could see a decent increase in performance that way.

Windows' swapfile usage is pretty similar to the way Linux does swap, except that Windows uses a file instead of a partition. By default it's 1.5 times the amount of RAM installed in the system and is made all at once to ensure a contiguous file. On systems with plenty of RAM it's still good to have because it means the OS can commit to having plenty of memory for applications which request a lot, most of which they might never use. Without a page file 10-20% of physical memory is wasted because the OS has committed to having it (think Photoshop, etc).

I don't know how well the pagefile would work on a USB drive since if you're using much swap you're already seeing serious degradation. Besides, flash drives still suck at write speeds, being many times worse than even an old IDE drive. That's the biggest problem with integrating the two technologies I would think--making sure that you don't introduce bottlenecks due to stuff like that.

Re:Maximum Writes for Flash Memory?

[DDLKermit007]

An age old method called write leveling. In practice it usualy doesn't work since most people do it with USB thumb drives and/or flash memorycards which are all removed on a regular basis so the reader/writer of the media gets changed allot or the controler doesn't impliment write leveling. As such the write leveling never really gets done very well. With a system like this the write leveling would be exact and the flash memory would end up outlasting the moveing parts of the hard-disk. Also as parts of the card went bad the controler would skip over those sectors in the future which would lead to it working even longer. Even one part of a regular hard disk goes bad and your boned completely.

Catastrophic Failure of Flash Memory

[reporter]

The technical specifications of the flash memory in my USB drive says that it is guaranteed to work for, at most, 100000 (i.e., one followed by 5 zeros) writes. People do not talk about this limitation, but I have seen this limitation written into the technical specifications of the flash memory in many devices.

The hard drive in my Compaq x86 workstation has been humming nicely for more than 5 years. Due to the nature of my work at the institute, the number of writes to the hard drive have easily exceeded 100000 during that time.

Using flash memory as a fast cache for the hard drive will increase the performance of the drive but will decrease the overall life of the drive. Someone will be awfully upset when she makes a final save of her million-dollar PowerPoint presentation for the CEO and discovers that the save is the 100001st write to the hybrid drive.

Hopefully, the engineer who designed this hybrid drive has, at a minimum, integrated an LCD counter and a tiny speaker into the drive. The counter shall display the running total of the number of writes to the flash memory. The tiny speaker shall beep like crazy when the total exceeds 99900.

Re:Catastrophic Failure of Flash Memory

[servognome]

Hopefully, the engineer who designed this hybrid drive has, at a minimum, integrated an LCD counter and a tiny speaker into the drive. The counter shall display the running total of the number of writes to the flash memory. The tiny speaker shall beep like crazy when the total exceeds 99900.

It was in the original engineering design, but the lawyers said it would be cheaper to just include a warning in the fine print of the warranty.

Re:Catastrophic Failure of Flash Memory

[Volante3192]

The technical specifications of the flash memory in my USB drive says that it is guaranteed to work for, at most, 100000 (i.e., one followed by 5 zeros) writes. People do not talk about this limitation, but I have seen this limitation written into the technical specifications of the flash memory in many devices

But, on the other hand, how often do you write to your windows folder? There's the monthly update, the occassional reg hack, but all in all, once it's established, that's a pretty static area of your drive. I could see this as an incredible benefit to system files, which, as has been discussed oft here before, the big reason for this.

Loading your PPT file in flash won't help bootup. Loading that fuster-cluck of the system32 folder, though, would.

Someone will be awfully upset when she makes a final save of her million-dollar PowerPoint presentation for the CEO and discovers that the save is the 100001st write to the hybrid drive.

Backups? Alternate locations? If this is what it takes for them to learn the necessity of redundant copies, it's even better.

There should be some level of safeguard built in that anything user created should be stored to the magnetic part of the drive, my documents, program files, but they should have this anyway. I mean, nothing like the last save and then having to call Dell because your drive is spitting out an Error Code 7...

Re:Catastrophic Failure of Flash Memory

[evilviper]

Someone will be awfully upset when she makes a final save of her million-dollar PowerPoint presentation for the CEO and discovers that the save is the 100001st write to the hybrid drive.

Yes. Everyone knows flash RAM will explode in a gigantic fireball on the 1st attempt to write to it, once it has gone beyond spec.

Re:Catastrophic Failure of Flash Memory

[flooey]

Using flash memory as a fast cache for the hard drive will increase the performance of the drive but will decrease the overall life of the drive. Someone will be awfully upset when she makes a final save of her million-dollar PowerPoint presentation for the CEO and discovers that the save is the 100001st write to the hybrid drive.

The thing to note is that that limitation is per flash block, not for the whole thing. So for a 1 GB flash component, given perfect block mapping, you can write around 100 TB of data to it before it wears out. With a 150MB/sec transfer rate, it would take more than a week of continuous writing to write that much. As well, modern flash can withstand a couple million writes, extending the life to several months of continuous writing. Given that this would generally be containing operating system components, which are read often but written to rarely, the lifespan of the memory should be no worry at all.

Re:Catastrophic Failure of Flash Memory

[Osty]

But, on the other hand, how often do you write to your windows folder? There's the monthly update, the occassional reg hack, but all in all, once it's established, that's a pretty static area of your drive. I could see this as an incredible benefit to system files, which, as has been discussed oft here before, the big reason for this.

Depends on what you're doing. For example, if you run IIS, your log files (by default; you can change this) are in %WINDIR%\Sytem32\LogFiles. That's going to have a lot of writes. Any new hardware or software installation may cause writes to %WINDIR%. There's a lot of other stuff that legitimately writes to %WINDIR% like installing a new printer (think roaming -- you may print to a different printer every day), the .NET Global Assembly Cache, Visual Styles and themes, and a whole lot more. Whether these things should be in %WINDIR% or not is a different question. The point is that using flash for %WINDIR% under the assumption that you'll not write there very often is a little naive. Perhaps Vista reorganizes %WINDIR% somewhat so that fewer processes need to write there.

There should be some level of safeguard built in that anything user created should be stored to the magnetic part of the drive, my documents, program files, but they should have this anyway. I mean, nothing like the last save and then having to call Dell because your drive is spitting out an Error Code 7...

All of this is a moot point anyway, because this use of flash is only as cache. Anything written to the flash drive should eventually be flushed to the hard drive. Similarly, if you've exhausted your write cycles and try to write to the cache, it should seamlessly catch the fault and go directly to hard drive. In that case it would be nice to give an occasional notice that your flash chip is exhausted and you need to replace it, but you should not risk losing any data. I'm not a big fan of on-board flash simply because it may be unreplaceable. Any onboard flash chips should not be surface-mounted, but socketed like RAM, CPU, or the clock battery. That will require some standardization on sockets, but as long as there are only two or three different options and the designers of said options let others build chips using that interface (*cough*Sony*cough*) it shouldn't be a problem.

In the long run, I think computer manufacturers will love this. How likely do you think your parents will be to replace their onboard flash when they run out of write cycles? The average consumer will just buy another PC for a couple hundred dollars rather than buying a new flash chip and installing it (or paying someone to install it).

How soon do you think the conspiracy theories will start up that manufacturers like Dell are intentionally shortening the life of onboard flash through factory "testing"?

Another benefit...

[mbstone]

Another benefit of hybrid drives is, you can use the carpool lane even if you're by yourself.

Re:Maximum Writes for Flash Memory?

[Eivind]

You're missing that the typical comercial flash-module is built to withstand 1 million writes or more.

A 1GB flash-module bein written to *constantly* (24 hours a day, 365 days a year) with a sustained speed of 5MB/s would thus wear out sometime after 6.5 *YEARS* of continous operation.

I'm guessing you can see why this problem is purely hypothethical for 99.99% of all laptops out there. You don't write to disc *constantly* and even if you did, you don't typically use the laptop 24/365, and even if you did, having a laptop-drive fail after 6-7 years is normally not a showstopper.

If, more realistically, the laptop is used 8 hours/day 250 days/years, and writes to disc 10% of the time when turned on, then the 1 million writes to flash will get reached after aproximately 30 years.

Even these numbers are high -- my laptop is heavily used as a developer workstation, and it certainly does not write to disc 10% of the time it is turned on.

Where to put the flash?

[Michael Woodhams]

The article discusses this. Intel want to put it on the MB, the drive manufacturers want to put it in the drive. A third option is to attach it separately and externally (e.g. a USB flash drive.) A final option would be to (e.g.) have a compact-flash-card (or similar) socket on the hard-drive, and users provide their own flash.

To my mind, the logical place to put it is on the drive. This is where the useful caching information is most easily available. (Which sectors are read/written how often? Which reads are often delayed by waiting for the disk to spin up?) This is also where you can make the process most transparent. The drive's firmware can make the system "just work", like a standard HD, but faster - whatever the OS, no drivers needed. (Although you'd possibly like to have drivers to give the OS more control over what is flash-cached.)

Re:Are standard file formats fine for use on flash

[I kan Spl]

Most filesystems are in fact optimized for use on magnetic media. Ext3 uses algorithms to place data on the disc in order to minimize the amount of waiting done for data.

There are research filesystems that are optimized for this kind of a hybrid environment. These were written for MEMS insetead of flash, but the basic ideas are nearly the same.

http://www.ssrc.ucsc.edu/proj/mems.html

Disclaimer: I work there. I may be biased.

Re:Finally...

[Knetzar]

I don't like that idea, since if a system failure occurs and I want to move my harddrive to another system, there is a chance that the harddrive is in a bad state. Where as if you have th flash integrated with the HDD, then the write buffer is with the disk (as it should be).

Massive disk cache

[nmg196]

We seem to be going backwards. About 10 years ago, I had a vesa local bus HDD controller which took SIMMS to use as cache. You could shove up to 32mb on it and it would remain powered even when the system was shut down. This meant you could load DOS and even Windows 3.11 entirely from the disk cache after rebooting. As far as I'm aware, there are no SATA controllers which can take DIMMS or similar to use as a large cache. PLEASE correct me if I'm wrong.

Why doesn't this exist today? I think it was a really good idea. The closest thing I've found is Gigabyte's iRam, but this isn't really the same thing - as it's purely a RAM drive and doesn't persist to hard disk.

I think that slow booting is the one of the biggest annoyances of computers and the primary reason many people never turn off their machines in an office environment (hiberating on XP rarely works reliably in my experience - usually due to driver issues not reinitialising the hardware properly rather than there being any problem with XP itself).

If people's machines booted to the desktop in under 10 seconds, far more people would turn them off at the end of the day and worldwide power consumption would be significantly reduced.

you're thinking of the wrong kind of flash...

[YesIAmAScript]

NOR flash (like the BIOS chip in your PC) is good for 1M writes or more.

But NOR flash is low density. An 8MByte NOR flash is large.

The flash that is being integrated into these drives is NAND flash. NAND flash is the kind of flash you use in your digital camera. NAND flash is high density.

And it is crap.

SLC NAND flash is good for 100,000 writes. But SLC is on the way out because it's only half as dense as MLC NAND flash. MLC NAND flash is good for 10,000 writes.

Are you scared yet?

That's a statistical measure, so often cells last longer than 10,000 writes before crapping out. And systems that use NAND flash use ECC (error correction codes) and wear levelling to try to hide the flash wearing out. It's complex, but it does work pretty well.

But a coworker made a flash burner app to wear out some flash on purpose. It wrote constantly. He able to wear it out in a couple days. It didn't wear out the entire flash chip, but that's when the flash started to develop sectors that were unusably bad, even with ECC.