Earlier quoted context omitted.
Yes. One can build a system that holds a petabyte of data, fits in less than one rack, has multiple redundancy, for about a hundred grand these days. Multiplied by three locations, that'll get you to $300000. Add in another $35000 for three years of hosting at three different datacenters, and you get to $335000. Sounds like a lot, right? Amazon's even more expensive. Storing one petabyte on Amazon, at the slowest, ch…
It costs about a hundred and fifty grand annually (fully loaded, base salary 80-90k) to have the lowest end person who could conceivably keep one of these things running well for three years. n+1 means you need two of them in case one gets the flu. Tell me again about how Amazon's a ripoff, please.
“Let's talk about a hypothetical public-facing service”
31–40 of 72 posts
Re: “Let's talk about a hypothetical public-facing service”
#32Earlier quoted context omitted.
> you can stop buying disks from Amazon every few months This is something that has been puzzling me. Many years ago I purchased 4x 2TB 5900 RPM drives for a 4 bay ReadyNAS (cost about ~$300 for drives plus ReadyNAS). They have been spinning nonstop for ~4 years [1] and haven't had to replace a single one. Not even an increase in errors to signal that the drive is going. Yet - I've worked on a SAN that cost hundreds…
AFR buddy, AFR. AFR is the annual failure rate, its typically 2 - 5% of the population per year. 4 drives you don't have a large enough set to see this in action, just every day you're in danger of losing a drive by a small statistical amount. In the Blekko cluster we have just under 10,000 drives. We have a two 20 drive 'boxes' (40 drives) from Western Digital, as drives fail we pull replacements from the 'new/refur…
Re: “Let's talk about a hypothetical public-facing service”
#33I was hoping they would stay offline. It's really disappointing to see a good service turn into a money wringing desperation.
I found myself in the odd position of hoping SF would come back up so I could finish what I was doing, when I'd normally welcome the news that they had shut down.
Re: “Let's talk about a hypothetical public-facing service”
#34Got a good chuckle. Such is life in IT. Gotta admit I missed the "Extremely Massive Corporation" hint.
It reminds me of Douglas Crockford's talk where he mentioned that a company asked him for an exemption to the "do no evil" clause in the JSON License, and he said he didn't want to name the company as that would embarrass them so he would instead give their initials: IBM.
Re: “Let's talk about a hypothetical public-facing service”
#35> You have a moment where you envision the future of virtualized storage and think about how great it will be when storage is nearly free and outsourceable and you can stop buying disks from Amazon every few months The future is now! Instead of you sending money to Amazon and them sending you disks, they keep the disks and you send them the money anyway. Progress! :-D
Sadly, depending on what you want to accomplish with your storage the future is still not here. For example, if you want to share a virtual disk with multiple servers through NFS you will still need to manually create a NFS high-availability cluster using e.g. DRBD on most cloud providers (e.g. EC2 or Azure). To be fair, MS Azure offers fully managed SMB shares as a service, but the transfer speed is quite low (60 MB…
Re: “Let's talk about a hypothetical public-facing service”
#36Earlier quoted context omitted.
It costs about a hundred and fifty grand annually (fully loaded, base salary 80-90k) to have the lowest end person who could conceivably keep one of these things running well for three years. n+1 means you need two of them in case one gets the flu. Tell me again about how Amazon's a ripoff, please.
You're still going to need n+1 sysadmins to maintain the rest of your infrastructure. Maintaining a storage system like this really isn't much different for the day-to-day operations. So, yes, it's one more system, but you're already going to need those admins anyways.
Re: “Let's talk about a hypothetical public-facing service”
#37Earlier quoted context omitted.
AFR buddy, AFR. AFR is the annual failure rate, its typically 2 - 5% of the population per year. 4 drives you don't have a large enough set to see this in action, just every day you're in danger of losing a drive by a small statistical amount. In the Blekko cluster we have just under 10,000 drives. We have a two 20 drive 'boxes' (40 drives) from Western Digital, as drives fail we pull replacements from the 'new/refur…
Just out of curiosity, has anyone done any research into determining whether a drive which fails after X days/years has some properties in the first Y days that could be a signal for future failure?
"In addition to presenting failure statistics, we analyze the correlation between failures and several parameters generally believed to impact longevity."
There is also a more recent open source dataset from Backblaze[2] that includes:
"Every day, the software that runs the Backblaze data center takes a snapshot of the state of every drive in the data center, including the drive’s serial number, model number, and all of its SMART data"
which forms the basis of an article correlating SMART data with drive failures at Backblaze[3].
[1]: http://static.googleusercontent.com/media/research.google.co...
[2]: https://www.backblaze.com/blog/hard-drive-data-feb2015/
Re: “Let's talk about a hypothetical public-facing service”
#38Earlier quoted context omitted.
You're still going to need n+1 sysadmins to maintain the rest of your infrastructure. Maintaining a storage system like this really isn't much different for the day-to-day operations. So, yes, it's one more system, but you're already going to need those admins anyways.
You're also going to need connectivity, of course. We were doing an apples to apples comparison in a vacuum, I thought.
Re: “Let's talk about a hypothetical public-facing service”
#39Earlier quoted context omitted.
Sadly, depending on what you want to accomplish with your storage the future is still not here. For example, if you want to share a virtual disk with multiple servers through NFS you will still need to manually create a NFS high-availability cluster using e.g. DRBD on most cloud providers (e.g. EC2 or Azure). To be fair, MS Azure offers fully managed SMB shares as a service, but the transfer speed is quite low (60 MB…
For sharing a filesystem between servers without managing your own high-availability cluster, you could try our ObjectiveFS [1]. [1] https://objectivefs.com
Re: “Let's talk about a hypothetical public-facing service”
#40Earlier quoted context omitted.
Sadly, depending on what you want to accomplish with your storage the future is still not here. For example, if you want to share a virtual disk with multiple servers through NFS you will still need to manually create a NFS high-availability cluster using e.g. DRBD on most cloud providers (e.g. EC2 or Azure). To be fair, MS Azure offers fully managed SMB shares as a service, but the transfer speed is quite low (60 MB…
Ec2 has efs at least, no idea if it's any good