SSHD for storage?

Solution
The SSD portion is meant to load system files that are accessed regularly to speed up the computer.

If you're just using it for storage there's really nothing that would be loaded to the SSD portion that would make any difference in the computer's performance.

SSHDs are best as an OS drives, NOT storage drives.
The SSD portion is meant to load system files that are accessed regularly to speed up the computer.

If you're just using it for storage there's really nothing that would be loaded to the SSD portion that would make any difference in the computer's performance.

SSHDs are best as an OS drives, NOT storage drives.
 
Solution

Karadjgne

Titan
Ambassador
The SSD portion of a hybrid SSHD is only 8Gb(?) So is used as a cache memory for fast file txfer, similar to Intel fast storage tech designs. So the hdd loads working files to the SSD, which then get worked in Windows and saved to the hdd as fast as it'll do it, all in the background. This is also exactly how a standard SSD OS-hdd storage system works, so using the hybrid with an SSD is just adding a step for nothing. Most hybrid drives also run 5900rpm, much slower than the 7200rpm standard. So while this can make the SSHD quieter and possibly cooler and more data reliable, its also possibly slower output by adding the extra step and slower speed.

The SSHD was designed as a stand alone unit, for those who want most of the SSD performance with the hdd capacity at a budget price and space requirement, vrs separate SSD and hdd.
 

Karadjgne

Titan
Ambassador
Yeah, Seagate has a super speed model, 2Tb I think it is.

Every command gets written through the OS, somewhere or another, even if it's just mouse or kb drivers. All that's on the OS SSD, which is great, really fast response times with read/write. Now when dealing with the storage drive, any data/files called for by the OS first have to be read on hdd, then written on OS. This is normal. Add the hybrid cache into the mix, and you read from hdd, written to cache, read from cache, written to OS, and any saved data goes in reverse, back through the cache first, as that's it's programming. So basically you just doubled the amount of time and workload to load the same info.

Considering the amount of time a SSD takes to move data, this may not seem like a big deal, but you also have to consider the amount of data moved in that time, and if you are running a high intensity graphics game, that's a huge amount of data moved,.... Twice. That equals lag.