4 ms·
How Facebook Squeezes More From Its Machines
- jsteele 17y agoOh no, have they started to embed scribd on web-pages. I absolutely hate scribd. Worst thing to hit the internet since that guy crying about Brittney Spears on youtube.
- s3graham 17y agoI love this Chrome extension: https://chrome.google.com/extensions/detail/nnbmlagghjjcbdhgmkedmbmedengocbn https://chrome.google.com/extensions/detail/nnbmlagghjjcbdhg... Solves PDF to ~99%.
- imurray 17y agoHere’s a user script that does a similar in thing for several browsers: http://www.cs.toronto.edu/~murray/code/#googleviewer http://www.cs.toronto.edu/~murray/code/#googleviewer
- rs 17y agoThe embedded paper is on Facebook's engineering notes as well: http://www.facebook.com/note.php?note_id=203367363919 http://www.facebook.com/note.php?note_id=203367363919
- houseabsolute 17y agoOnly 30,000? I would have guessed much more.
- grinich 17y agoThey're all in the US, too.
- Andys 17y agoWonder how many of them are just almost idle, running something like memcached?
- lsb 17y agoFacebook's actually encountered scaling problems from memcached taking up too much CPU time; that's why there's the binary protocol, and they're talking about the multiget hole at http://highscalability.com/blog/2009/10/26/facebooks-memcached-multiget-hole-more-machines-more-capacit.html http://highscalability.com/blog/2009/10/26/facebooks-memcach...
- koko775 17y agoAnd you'd be right. That figure is way old, and even small for then.
- mtw 17y agoany link with more info about Dyno? the article assumes readers know about this testing tool.