{"id":645361,"date":"2013-03-05T19:13:10","date_gmt":"2013-03-06T00:13:10","guid":{"rendered":"http:\/\/gigaom.com\/?p=617081"},"modified":"2013-03-05T19:13:10","modified_gmt":"2013-03-06T00:13:10","slug":"facebook-kisses-dram-goodbye-builds-memcached-for-flash","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/645361","title":{"rendered":"Facebook kisses DRAM goodbye, builds memcached for flash"},"content":{"rendered":"

Q:\u00a0What do you get when you mix Facebook\u2019s extensive memcached usage with its strategy of \u201ccold storage\u201d for infrequently accessed data?<\/p>\n

A: McDipper, a Facebook-built implementation of the popular memcached key-value store designed to run on flash memory rather than pricier DRAM.<\/p>\n

Memcached<\/a>, for the unfamiliar, is an open-source key-value store that caches frequently accessed data in memory so applications can access and serve it faster than if it were stored on hard disks. It\u2019s a very popular component of many web applications stacks, including at Facebook where the company runs thousands of memcached servers to power its various applications.<\/p>\n

But DRAM is expensive, especially when you get to Facebook\u2019s scale, and not all applications deserve that kind of performance. So, according to a Facebook Engineering post on Tuesday<\/a>, the company designed McDipper to handle \u201cworking sets that had very large footprints but moderate to low request rates. \u2026 Compared with memory, flash provides up to 20 times the capacity per server and still supports tens of thousands of operations per second.\u201d<\/p>\n

Facebook has deployed McDipper for a handful of these workloads, the blog states, and\u00a0has \u201creduced the total number of deployed servers in some pools by as much as 90% while still delivering more than 90% of get responses with sub-millisecond latencies.\u201d It has been part of Facebook\u2019s photo infrastructure for about a year and serves 150 gigabits of data per second \u2014 or \u201cabout one library of congress (10 TB) every 10 minutes\u201d \u2014 over Facebook\u2019s content-delivery network.<\/p>\n

\"mcdipper\"<\/p>\n

How McDipper stores data<\/p>\n<\/div>\n

This is the same logic that drove Facebook to undertake its cold storage engineering effort<\/a> for even more infrequently accessed data, which aims to find a middle ground between the inefficiency and latency of hard disks and the high cost of flash storage. To meet that goal, the company is getting creative by considering everything from lower-performance flash to Blu-ray<\/a> \u2014 pretty much anything but tape \u2014 VP of Engineering Jay Parikh told me in January.<\/p>\n

Building a tool like McDipper is the just the tip of the iceberg, though, when it comes to managing the cost and efficiency of infrastructure at large web companies such as Facebook. On Tuesday, eBay released its Digital Service Efficiency report<\/a> that lays out a methodology for assessing the effect that infrastructure (more than 52,000 servers in eBay\u2019s case; Facebook has even more) has on larger corporate goals such as clean energy and the bottom line.<\/p>\n

And later this month at our Structure: Data conference<\/a>, data center executives from Facebook, Microsoft and Goldman Sachs will take the stage to discuss how smart analytics help them plan to meet capacity needs while keeping costs in check.<\/p>\n

Feature image is Facebook\u2019s new all-flash Dragonstone server design.<\/em><\/p>\n

\"Structure:Data:<\/a><\/p>\n

\"\"<\/p>\n

<\/a><\/p>\n

Related research and analysis from GigaOM Pro:<\/strong>
Subscriber content. Sign up for a free trial<\/a>.<\/p>\n