A Hybrid Approach For SSD Speed From Your 2TB HDD
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!"
Haven't disk manufacturers been doing this forever, using faster memories to cache disk? I guess the difference now is that the memory is slower than DRAM and non-volatile so it isn't lost in the event of power failure? Or maybe you can get more flash storage at a low price point?
-- Erich
Slashdot reader since 1997
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?
Eloi are stupid, throw morlocks at them!
No software or driver update is required
Some software is needed to achieve the magic
I DNRTFA, but this really just seems like a fancy version of cache to me....
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.
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.
"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).
---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"
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.
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.
Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
// You sound jealous...
You place too much value on a single drive bay. Buy a larger case already.
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.
While that is true in many cases, when one drive dies you will get much better read and write performance out of RAID 1 than RAID 0.