3 ms·
Facebook didn't do it with "crusty old PHP;" rather, they had to re-build their stack completely from scratch to keep up. See HipHop, their homegrown PHP-to-C c
by gcr 16y ago
Facebook didn't do it with "crusty old PHP;" rather, they had to re-build their stack completely from scratch to keep up. See HipHop, their homegrown PHP-to-C compiler https://github.com/facebook/hiphop-php/wiki/ https://github.com/facebook/hiphop-php/wiki/ and Cassandra, their own custom database system http://cassandra.apache.org/ http://cassandra.apache.org/
If they stuck with crusty old PHP, I have no doubt they would never be able to manage the load.
- samt 16y agoNo kidding. They're using php as a template language to call thrift services. That's hardly "using php" in the sense that most people would think of it.
- antidaily 16y agoCould anything "off-the-shelf" have managed that load?
- Kafka 16y agoIt depends on how many servers you are willing to run. When you have 500 million users, and a decent amount of them, accesses your site multiple times a day, CPU cycles per request starts to count.
- ssharp 16y agoAre there any websites that face similar load problems to Facebook's that are addressing it with an unmodified stack?
- rorrr 16y agoI'm pretty sure Facebook's bottleneck is the database, not the framework.
- benologist 16y agoBack when MySpace actually mattered I don't think they had HipHop, Cassandra etc.
- nikcub 16y agoHipHop went live on FB last year. It didn't even go live everywhere at once. For some reason ppl think Mark created it on the 3rd day