GitHub - facebook/mcrouter: Mcrouter is a memcached protocol router for scaling memcached deployments.You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Scaling Memcache at Facebook | USENIX
by Michael Piatek Responsiveness is essential for web services. Speed drives user engagement, which drives revenue. To reduce response latency, modern web services are architected to serve as much as possible from in-memory caches. The structure is familiar: a database is split among servers with caches for scaling reads. Over time, caches tends to accumulate more responsibility in the storage sta
http://qcontokyo.com/pdf/qcon_MarcKwiatkowski.pdf
memcache@facebook Marc Kwiatkowski memcache tech lead QCon 2010 How big is facebook? 400 million active users M 90M 180M 270M 360M 450M 2008 400 M Objects ▪ More than 60 million status updates posted each day ▪ 694/s ▪ More than 3 billion photos uploaded to the site each month ▪ 23/s ▪ More than 5 billion pieces of content (web links, news stories, blog posts, notes, photo albums, etc.) shared ea
Facebook's Memcached Multiget Hole: More machines != More Capacity - High Scalability -
When you are on the bleeding edge of scale like Facebook is, you run into some interesting problems. As of 2008 Facebook had over 800 memcached servers supplying over 28 terabytes of cache. With those staggering numbers it's a fair bet to think they've seen their share of Dr. House worthy memcached problems. Jeff Rothschild, Vice President of Technology at Facebook, describes one such problem they
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
https://www.usenix.org/system/files/conference/nsdi13/nsdi13-final170_update.pdf
Facebookにログイン
