4 ms·
And still making an easy profit. Calculating it through, I think they make about $5 profit per terabyte per year, and that's using normal prices that I'd pay f
by lucb1e 13y ago
And still making an easy profit.
Calculating it through, I think they make about $5 profit per terabyte per year, and that's using normal prices that I'd pay for hardware and power as a consumer in America.* That is considering costs for: buying drives (with a mean time to failure of 2 years), buying a server, power for the server and drives, and storing the data with 3x redundancy (two drives can fail and a third and fourth still have it).
* "In America" must be noted because power is dirt cheap there. Like .09 dollar per kWh while here we pay .2 euros.
I'm thinking of starting an online backup service myself for a fair price and no corporate bullshit, but as a student with no money nor experience I'm very hesitant. But I might try!
- daave 13y ago3x redundancy is very cost ineffective. See this 2010 Google presentation (slide 13) on the 'Colossus' File System, which uses Reed-Solomon encodings. http://static.googleusercontent.com/media/research.google.com/en/us/university/relations/facultysummit2010/storage_architecture_and_challenges.pdf http://static.googleusercontent.com/media/research.google.co... There's really a need for a good open-source equivalent to Colossus, which would allow startups like the hypothetical one you describe to do storage must more cheaply and reliably. HDFS (with HDSF-RAID) is probably the closest.. but it's still a long way off. I'd be interested in what other assumptions you're using to come up with the $5/T profit margin. Are you considering the cost of ingress and egress bandwidth, cooling, personnel to enact repairs? With a large enough fleet you'll have many drives/machines die every day. What about a team of engineers in an on-call rotation to keep to respond when (inevitable) failures occur? Just pointing out that drives + power is only part of the total cost of running such a service.