News for hackers. Stuff that matters.
Re:Flash Drives Replace Disks at Amazon, Facebook, Dropbox by ajross on Wednesday June 13, 2012 @02:56PM (#4107762)
I'm not sure I buy this as a good idea quite yet. Flash is, right now, about 8x cheaper than DRAM per storage and 10x more expensive than disks. And the DRAM latency is, of course, about 1000x better still.

Basically for many workloads, it's now (edited: original said "not" -- oops) possible to fit entire data sets in RAM, backed by cheaper traditional disks that essentially just stream write logs.

And for workloads where storage costs actually dominate (I'm thinking youtube/dropbox type stuff) it seems like access is mostly streaming, where HD performance is actually quite good.

Obviously SSDs make a ton of sense in the consumer space, where you only get one drive. But if you could pick your RAM/Flash/Disk mix yourself and tailor it to your app, I guess I don't see a lot of advantage to putting your money into the "middle" of that stack.

Re:Flash Drives Replace Disks at Amazon, Facebook, Dropbox by jchrisa on Wednesday June 13, 2012 @07:28PM (#4109030)
At scale, disk throughput more than anything else will dominate. How long do you want backups to take? If ssds are faster they might mean fewer servers with more disk throughput per server can give users a snappier experience.
Re:Flash Drives Replace Disks at Amazon, Facebook, Dropbox by excuse-me on Wednesday June 13, 2012 @03:02PM (#4107792)
Especially since the article suggests that most of the SSDs are being used for meta-data / content-management with the actual data being on spinning disks, possibly in another data center.

Since they have so much lower power demands I wonder if they are going to move further up the pipe? Instead of the ISP routing a request to an index server which then decides which is the nearest DC or akaimai host with the actual data - would the first line of dropbox/amazon/google/netflix actually move into the ISP's local rack.