Engineering @ Facebook's Notes | Facebook - The Diigo Meta page

• 04 Dec 09
  

  Damon Snyder

  facebook image storage infrastructure architecture

• 29 Sep 09
  

  Navneet Kumar

  READ WRITE Performance

  FaceBook Infrastructure Architecture Hardware Performance Read-Write

  • Since each image is stored in its own file, there is an enormous amount of
    metadata generated on the storage tier due to the namespace directories and file
    inodes. The amount of metadata far exceeds the caching abilities of the NFS
    storage tier, resulting in multiple I/O operations per photo upload or read
    request. The whole photo serving infrastructure is bottlenecked on the high
    metadata overhead of the NFS storage tier, which is one of the reasons why
    Facebook relies heavily on CDNs to serve photos
  • RAID-6 partition managed by the hardware RAID controller. RAID-6 provides
    adequate redundancy and excellent read performance while keeping the storage
    cost down
  • 1 more annotations...
  • • The poor write performance is partially mitigated by the RAID controller NVRAM
      write-back cache. Since the reads are mostly random, the NVRAM cache is fully
      reserved for writes. The disk caches are disabled in order to guarantee data
      consistency in the event of a crash or a power loss
• 26 May 09
  

  Alex Popescu

  Needle in a haystack: efficient storage of billions of photos

  architecture highscalability Facebook

• 04 May 09
  

  sven duzont

  facebook storage

• 02 May 09
  

  geheimdienst

  dev scale

• 

  Joel Liu

  facebook Architecture photo storage

• 01 May 09
  

  makoto tsuyuki

  facebookの新しい写真保存ストレージの仕組み解説（詳細）
  
  より詳細なオフィシャル解説
  
  藁の山から針を探す

  storage distributed

• 

  Jungho Kim

  architecture performance data

• 

  Matt Cox

  The Photos application is one of Facebook’s most popular features. To date, users have uploaded over 15 billion photos which makes Facebook the biggest photo sharing website. For each uploaded photo, Facebook generates and stores four images of different sizes, which translates to a total of 60 billion images and 1.5PB of storage. At the peak there are 550,000 images served per second. This blog post explains how they do it.

  peter vajgel blog facebook storage photo photo sharing geeky social networking infrastructure

  • Facebook generates and stores four images of different sizes, which translates to a total of 60 billion images and 1.5PB of storage. The current growth rate is 220 million new photos per week, which translates to 25TB of additional storage consumed weekly. At the peak there are 550,000 images served per second.

    • 

      Matt Cox on 2009-05-01

      Woah! That's some serious bandwidth.
• 

  Ankit Mishra

  facebook

Public Stiky Notes

• 
  Matt Cox on 2009-05-01
  Woah! That's some serious bandwidth.

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.