How Facebook Squeezes More From Its Machines

Oh 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.

I love this Chrome extension: https://chrome.google.com/extensions/detail/nnbmlagghjjcbdhg...

Solves PDF to ~99%.

Here’s a user script that does a similar in thing for several browsers: http://www.cs.toronto.edu/~murray/code/#googleviewer

The embedded paper is on Facebook's engineering notes as well:

http://www.facebook.com/note.php?note_id=203367363919

Only 30,000? I would have guessed much more.

They're all in the US, too.

Wonder how many of them are just almost idle, running something like memcached?

Facebook'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-memcach...

And you'd be right. That figure is way old, and even small for then.

any link with more info about Dyno? the article assumes readers know about this testing tool.