views:

184

answers:

2

This may be slightly off-topic for a strictly programming site, but I'm interested in starting a software project or contributing to an existing project that can do what I'm proposing.

Now that SSD storage is becoming more popular, I am more interested in using one in my destop computer. Since they are very expensive per Gigabyte compared to standard drives, I must limit the size of the drive. I want to maximize the use, but can't place all of my data on it.

What I would like to do is use the SSD as an invisible inline cache to the rest of my data without having to explicitly store data on it. As data is read from my normal drive, it is cached to the SSD. All subsequent access to these files will retrieve it from the SSD, and any changes will propagate down to the slower drive. The user would never see the SSD in their list of drives.

In this way, the first time you access a file, it may be slightly slower than usual, but from that point on, it will be much faster. Obviously, after a while the SSD will fill up, and less frequently used files can be released to make room.

Are there any filesystems out there that allow for something like this, or is it feasible have a low-level driver do the work between the OS and the filesystem?

A: 

You should be asking that on serverfault.com

Bryan Migliorisi
Thanks. I've never been there. I'll check it out.
Tim Rupe
A: 

Ditto what Bryan said about belonging on server fault. However, while here I would strongly suggest you do not use an SSD drive as a cache drive.

SSD drives start off running pretty fast. However, over time they slow down because overwriting data on the drive is an extremely slow operation. Traditional drives will always win out in this situation.

The only time I would consider using an SSD drive is if 1. I could afford a huge drive and therefore wouldn't run into the overwriting penalty; or 2. If the data was fairly static on the drive after it was loaded; or 3. If speed wasn't that important while survivability in adverse conditions was (car computer for example).

None of these situations seem to be what you're after, so I'd say keep your money. The latest 1.0 and 1.5 TB drives are cheaper and extremely fast now anyways. Look into one of those.

Chris Lively
I didn't -1 this response. I'm not sure this is necessarily true any more, though; modern SSDs support the TRIM command. On the other hand, presumably the drive would stay mostly full. Reading data should still be fast and offer extremely low latency, but replacing items in the cache would indeed suffer the rewrite penalty. Still, that penalty still leaves you with a drive that is faster at 4 KB random writes compared to mechanical drives like the Raptor, so it may still be a net win.
ChrisInEdmonton