http://highscalability.com/blog/2007/11/13/friendster-lost-l...
VB: Can you tell me a bit about what you learned in your time at Friendster?
JS: For me, it basically came down to failed execution on the technology side — we had millions of Friendster members begging us to get the site working faster so they could log in and spend hours social networking with their friends. I remember coming in to the office for months reading thousands of customer service emails telling us that if we didn’t get our site working better soon, they’d be ‘forced to join’ a new social networking site that had just launched called MySpace…the rest is history. To be fair to Friendster’s technology team at the time, they were on the forefront of many new scaling and database issues that web sites simply hadn’t had to deal with prior to Friendster. As is often the case, the early pioneer made critical mistakes that enabled later entrants to the market, MySpace, Facebook & Bebo to learn and excel. As a postscript to the story, it’s interesting to note that Kent Lindstrom (CEO of Friendster) and the rest of the team have done an outstanding job righting that ship.
But the board also lost sight of the task at hand, according to Kent Lindstrom, an early investor in Friendster and one of its first employees. As Friendster became more popular, its overwhelmed Web site became slower. Things would become so bad that a Friendster Web page took as long as 40 seconds to download. Yet, from where Mr. Lindstrom sat, technical difficulties proved too pedestrian for a board of this pedigree. The performance problems would come up, but the board devoted most of its time to talking about potential competitors and new features, such as the possibility of adding Internet phone services, or so-called voice over Internet protocol, or VoIP, to the site.
The stars would never sit back and say, ‘We really have to make this thing work,’ ” recalled Mr. Lindstrom, who is now president of Friendster. “They were talking about the next thing. Voice over Internet. Making Friendster work in different languages. Potential big advertising deals. Yet we didn’t solve the first basic problem: our site didn’t work.”
Why would you do that?
This is bread & butter algorithm analysis. Don't put O(n^2) analyses on your most-loaded page.
Others in the company begged to at least back it down to a count of people 2 degrees away; but the founder insisted that the magic was the 3-degree version. So instead the company pursued technical strategies to speed up the 3-degree count; don't know what those were precisely, but it seems that they were not pursued as zealously as they could be (due to VoIP, etc. distractions).
My understanding, by the way, is that the network size was computed on page-load until surprisingly very late, due to the perceived need for real-time. Even after it was cached, it was still computationally expensive, as your numbers were computed (roughly) every time your 3-degree network added a link.
In retrospect, A/B testing could have been used to test the executive vision. So although my first reaction upon hearing this story (years ago) was: "that's big-O insanity," now I think that it's just as much a story about willingness to subject vision to empirical data and performing clinical cost/benefit analysis (when appropriate).
Funnily enough, now I think about it, performance may be much more critical than periods of downtime.
Bad products tend to die or get replaced by superior offerings. Thats the nature of business.
Not being able to innovate rapidly because of technical lock in is the only way these types of issues can "kill" a site. But its very hard to quantify these types of issues. Between this article and Kevin Rose's statements about hiring B&C level programming talent it seems like a lot of engineers are getting tossed under buses, for poor management decisions.