Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, that is the real question I have about SSD; I mean, normally you want to buy enough ram to cache all the data you regularly access, because the overhead of hitting spinning disk absolutely kills you.

Now, SSD is still slower than ram... way slower than ram. But it's way faster than spinning disk, especially on reads. I imagine there are some applications where SSD is fast enough that hitting disk is okay; you don't need to worry about having enough ram to cache all data you might read, and ram is still like eight or nine bucks a gig (vs. $0.6 to $2 for mlc ssd) - and if we're talking about reads here? MLC is fine for reads.

Of course, part of that ram difference might be that ram prices haven't fallen much over the last year or two, (in fact, most of the ram I bought last year, I bought at a lower price than the ram I'm looking at now.) while SSD prices have really fallen fast, so I don't know if this is the long-term price-equilibrium; still, I would expect ssd to continue to be significantly less expensive than ram.



What do you use for caching that uses the hard drive? Redis?


No, I was talking about caching disk reads in ram. Nearly all modern operating systems do this. If you have enough ram, the data you read from disk is cached in ram. With spinning disk, especially shared 7200rpm spinning disk, for interactive use? generally speaking, you have human-noticeable latency every time you do a blocking read that isn't cached.

Because of this, having enough ram to cache all the data you read often is extremely important to system performance when you are on spinning disk. (and having a pagecache that doesn't dump all the stuff you use often when you do a one-time read of a big file.)

I was suggesting that SSD might have fast enough read-access that for some applications, the penalty for reading from ssd rather than from pagecache might be small enough to not be a big deal, meaning you could get acceptable performance out of a system with less total ram.


Thanks for clarifying. I was wondering about Redis because it doesn't replace cached contents when there's no memory left, like Memcached.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: