I find the introduction of a hybrid polling/interrupt driven network interface really interesting. Mainly because we did the same work in 2003 on NetBSD for a wireless router that never made it to market. We were at the opposite end of the spectrum. Basically, we were running on a 100 MHz 486 and spent too much time on interrupts with all the network traffic. It's funny that it is the same situation for them on the latest systems out there (of course for some of the same, but some different reasons as well).
Scaling memcached at Facebook
11–12 of 12 posts
Re: Scaling memcached at Facebook
#12I must say, Facebook does a lot of interesting work. Things that hardcore engineers would definitely enjoy doing. But also things I would hate to support. For instance, I would NEVER want to have to support making a one-off change to MySQL as Facebook has done, to enable them to open a new data center ( http://www.facebook.com/note.php?note_id=23844338919&id=... ). What happens when MySQL is updated? They can no long…
You really think a site the scale of Facebook just pulls the latest version of mySQL and deploys it? I think even smaller sites like Smugmug put new releases through extensive testing before deployment. It seems to me that pulling the source, applying their patch and building is probably a pretty small part of the effort of rolling out a new version.