A Hybrid Approach For SSD Speed From Your 2TB HDD 194
Claave writes "bit-tech.net reports that SilverStone has announced a device that daisy-chains an SSD with a hard disk, with the aim of providing SSD speeds plus loads of storage space. The SilverStone HDDBoost is a hard disk caddy with an integrated storage controller, and is an easy upgrade for your PC. The device copies the 'front-end' of your hard disk to the SSD, and tells your OS to prefer the SSD when possible. SSD speeds for a 2TB storage device? Yep, sounds good to me!"
Just a cache? (Score:5, Insightful)
Re:Save your money... (Score:2, Insightful)
I don't see where a 2.5" HD is required - 3.5" should be fine. The gizmo looks like a 2.5" to 3.5" adapter tray, but the HD is not installed in the gizmo.
Besides, have you ever heard of a 2.5" 2TB drive?
Pick the false statement (Score:5, Insightful)
No software or driver update is required
Some software is needed to achieve the magic
Isn't this just a fancy cache? (Score:1, Insightful)
I DNRTFA, but this really just seems like a fancy version of cache to me....
Re:Isn't this just a fancy cache? (Score:3, Insightful)
No, it's a simple version of cache that doesn't actually do proper caching. All it does is preloading, and only over part of the device. Most of the volume of the hard disk will have no performance boost at all. You'd almost certainly be better off just having two devices, and using junction points on Windows or soft links on UNIX to move the frequently accessed files to the smaller disk.
Re:Just a cache? (Score:3, Insightful)
"DRAM is yesterday's news. SSDs are the future. And they cost a lot more than a pile of memory chips, therefore they must be better. Order fifty." -- Some PHB
SSDs are cheaper per Gb then DRAM. Compare the price of a 64Gb SSD to 64Gb with of decent DDR2/3 RAM. The per-Gb price difference is likely to grow too as SSD prices are falling more sharply than DRAM prices at the moment.
Waste of money and data safety (Score:3, Insightful)
Now, maybe you could do it safely if the device had RRD ram to handle the caching, SSD flash ram to handle power outages, a rechargable battery or ultra cap to provide power to write the RRD ram to flash ram after a power outage, and a controller to handle all this. You would need to implement all the normal os buffer caching and writebacks as well.
File system (Score:1, Insightful)
There was a paper some years ago about building the file system in such a manner that smaller files were placed on an SSD ( 1 MB) and large files were placed on a harddisk. At that time, SSDs were a lot smaller than today though.
Generally, it can make sense to discriminate your files because they don't all have the same space and access characteristics. Maybe 100 files is taking up 90% of the space compared to the other 9900 files. Maybe it's similar for the access pattern.
Still, for the idea to fly, you need to a robust algorithm and it needs to be clever about the strengths of the hardware. For instance, SSDs aren't so hot at random writes, sadly. Less than 0.1 msec write time would be neat for an ACID database.
Re:Holy carp! (Score:3, Insightful)
"Very specific needs" like wanting my OS & apps to load as fast as possible? Putting OS, apps, pagefile etc on the SSD greatly improves system responsiveness. FLACs, MP4s & JPGs can stay on a spinning disk, I don't need to access them so quickly. A couple hundred bucks on a smallish SSD gives you a MUCH better performance kick that spending the equivalent on RAM or CPU, in my experience (provided of course you have at least an average spec machine to start with).
Re:Waste of money and data safety (Score:3, Insightful)
Would it not be more cost effective to add more main memory to the machine?
I've never had a machine with capacity for more than 12GB RAM.
Also I have a concern that frequently updated blocks (like your file system superblocks) would not get written out to disk in a timely fashion.
That's a bigger problem with your RAM-based approach than with a flash-based one.
Now, maybe you could do it safely if the device had RRD ram to handle the caching, SSD flash ram to handle power outages, a rechargable battery or ultra cap to provide power to write the RRD ram to flash ram after a power outage, and a controller to handle all this.
You can get this with ZFS, a DRAM disk with a backup battery (volatile disks do exist that you load with DIMMs) and a caching raid controller with a backup battery.
Impressive is that it works with Windows (Score:4, Insightful)
There is nothing new or impressive about this device.
Other than that it is compatible with applications and peripheral drivers designed to run on the majority operating system for home and office PCs, which has no support for ZFS.
Re:Save your money... (Score:3, Insightful)
If you RTFA you'd find the 2.5" drive is for the SSD, not the rotational drive.
The bracket mounts the SSD inside of it, and then passes failed requests to the HDD, which is external to the bracket.
Re:Your sig (Score:4, Insightful)
// You sound jealous...
Re:Save your money... (Score:1, Insightful)
Already do! rootfs on SSD, home/huge on disk (Score:3, Insightful)
There are alignment tricks with SSD around their large erase blocks, so you have to be careful partitioning.
Also, consumer-grade MHC SSDs are _not_ tremendously faster than spinning disks in transfer speed. Maybe 20%. Access time is where SSDs shine, 0.2 ms vs 8-10ms .
A simple scheme I use is to put the OS & small, frequent datafiles on SSD, and large [image] files on platter.
This might not help large databases with sparse access, but lots of RAM disk cache should be better. IIRC Seagate had a disk with flash boost, but had trouble with it.
Re:Holy carp! (Score:3, Insightful)