MessiandNeymar

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, July 24, 2012

Simple hardware lessons for a software guy, part 3

Posted on 7:17 AM by Unknown

Good things come in threes, right? So this poor software guy is happy that he's had some great opportunities to learn about hardware over the last few days.

The third of three is Robin Harris's fascinating article: The post-RAID era begins.

Harris starts out by pointing out that simple RAID 5 algorithms are failing to scale due to the immense growth in disk capacity.

He proceeds to discuss the substantial progress that is being made in "erasure coding", which involves new ways of encoding stronger parity checks into your data.

In the ’90s a new form of erasure coding was developed that enabled developers to create codes with an arbitrary level of redundancy – survive 4 failures? 10? Pick a number! – called fountain or rateless erasure codes.

Harris suggests that in the (near) future, storage systems will no longer be using simple RAID techniques, but instead will be using the more sophisticated erasure coding technology, and references a number of startups who are active in this area.

Harris also links to a nice presentation by Professor Jim Plank of the University of Tennessee: Erasure Codes for Storage Applications.

The Point of This Tutorial
  • To introduce you to the various erasure coding techniques.
    • Reed Solomon codes.
    • Parity-array codes.
    • LDPC codes.
  • To help you understand their tradeoffs.
  • To help you evaluate your coding needs.
    • This too is not straightforward.
Professor Plank is not kidding about the coding needs being "not straightforward": by the fifth page of his paper A Tutorial on Reed-Solomon Coding for Fault-Tolerance in RAID-like Systems we're into arithmetic over Galois Fields...

Professor Plank's web site is loaded with lots of additional information about erasure coding.

Thus ends our short three-part series of the software guy learning more about hardware...

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Shelter
    I meant to post this as part of my article on Watership Down , but then totally forgot: Shelter In Shelter you experience the wild as a moth...
  • The Legend of 1900: a very short review
    Fifteen years late, we stumbled across The Legend of 1900 . I suspect that 1900 is the sort of movie that many people despise, and a few peo...
  • Rediscovering Watership Down
    As a child, I was a precocious and voracious reader. In my early teens, ravenous and impatient, I raced through Richard Adams's Watershi...
  • Must be a heck of a rainstorm in Donetsk
    During today's Euro 2012 match between Ukraine and France, the game was suspended due to weather conditions, which is a quite rare occur...
  • Beethoven and Jonathan Biss
    I'm really enjoying the latest Coursera class that I'm taking: Exploring Beethoven’s Piano Sonatas . This course takes an inside-out...
  • Starting today, the games count
    In honor of the occasion: The Autumn Wind is a pirate, Blustering in from sea, With a rollocking song, he sweeps along, Swaggering boisterou...
  • Parbuckling
    The enormous project to right and remove the remains of the Costa Concordia is now well underway. There's some nice reporting on the NP...
  • For your weekend reading
    I don't want you to be bored this weekend, so I thought I'd pass along some articles you might find interesting. If not, hopefully y...
  • Are some algorithms simply too hard to implement correctly?
    I recently got around to reading a rather old paper: McKusick and Ganger: Soft Updates: A Technique for Eliminating Most Synchronous Writes ...
  • Don't see me!
    When she was young, and she had done something she was embarrassed by or felt guilty about, my daughter would sometimes hold up her hand to ...

Blog Archive

  • ►  2013 (165)
    • ►  September (14)
    • ►  August (19)
    • ►  July (16)
    • ►  June (17)
    • ►  May (17)
    • ►  April (18)
    • ►  March (24)
    • ►  February (19)
    • ►  January (21)
  • ▼  2012 (335)
    • ►  December (23)
    • ►  November (30)
    • ►  October (33)
    • ►  September (34)
    • ►  August (29)
    • ▼  July (39)
      • Serious infrastructure issues
      • Drone pilots in the NYT
      • Nice Olympics sailing video
      • Inside the Coursera contract
      • Networking: theory and practice
      • The other Eagle
      • Precious Reynolds and the Milwaukee Protocol
      • Trying to understand the evolution of finance
      • Who invented the Internet, part 94
      • Annie Hall, now and then
      • Simple hardware lessons for a software guy, part 3
      • Simple hardware lessons for a software guy, part 2
      • Simple hardware lessons for a simple software guy
      • The bubble is back!
      • It's not just a game ...
      • Random stuff I'm reading currently
      • Solomon's Oak: a very short review
      • Postcards from the high end...
      • Some Dallas phone numbers are not Dallas phone num...
      • Perforce 2012.2 has entered beta testing
      • Good enough for GitHub
      • The Coursera Tsunami
      • A collection of AWS post-mortems
      • Java code coverage and thrown exceptions
      • Google Summer of Code and the University of Moratuwa
      • Construction Everywhere
      • MMDS 2012
      • Tips for security conference week
      • GSoC 2012: halfway there!
      • Various database topics
      • A troubling article on scientific careers
      • ubuntu tracker and locate
      • So that's what it takes to find a Higgs Boson!
      • And now we will know for sure
      • Silicon Valley craziness
      • Matthew Yglesias on patent "reform"
      • Post-vacation link dump
      • A week in Kauai
      • I'm back online
    • ►  June (27)
    • ►  May (48)
    • ►  April (32)
    • ►  March (30)
    • ►  February (10)
Powered by Blogger.

About Me

Unknown
View my complete profile