Re:Where SSDs Don't Make Sense in Server Applications
by andr on Sunday April 12, 2009 @04:10PM
(#558820)
I guess the real questions is are SSDs good enough to replace data that now sits in RAM? For example, Google keeps their entire search index in RAM. Would they be better off keeping it in SSDs?
[ Parent
| on HN ]
Re:Where SSDs Don't Make Sense in Server Applications
by wheels on Sunday April 12, 2009 @04:39PM
(#558845)
Not even close. The bandwidths of RAM vs. SSDs differ by a couple orders of magnitude.
Re:Where SSDs Don't Make Sense in Server Applications
by krschultz on Sunday April 12, 2009 @04:48PM
(#558861)
Especially with the Intel X-25 at around $4.50 per GB and DDR2 running at $10 per GB - there just isn't much of a cost savings for completely disparate performance.
Re:Where SSDs Don't Make Sense in Server Applications
by wmf on Sunday April 12, 2009 @06:33PM
(#559002)
When you calculate the price of RAM, consider the slots as well. Putting a TB of RAM in a server requires more than just DIMMs.
Re:Where SSDs Don't Make Sense in Server Applications
by bayareaguy on Sunday April 12, 2009 @06:43PM
(#559015)
But as the paper linked by the article[1] points out, a single server can hold much more data in SSD storage then in onboard RAM.
For ordinary databases, one sweet spot for SSDs is for index tablespaces.
[1] - http://research.microsoft.com/en-us/um/people/antr/ms/ssd.pd...