IssueRaiser
All solutions

Ocelot: The story of a torrent tracker

I took this directly from a newspost on what.cd, and I have no association with anything written here. Just thought HN would find it interesting. What.CD is a private tracker. Thus, the entire site, staff, and community all revolve around a common piece of software - the tracker backend. Complementing the site frontend, which you're looking at now, the tracker itself handles connections between peers. With over five million peers, our tracker receives an average of 3,500 hits per second, although after a period of tracker downtime, load can spike up to past 12,000 hits per second. This means that, when your client announces, the tracker has 80 microseconds to search through its database of over 900,000 torrents and 5,000,000 peers, compute a response, and send it back to you. That's a lot of stress on a piece of software! We anticipated this problem, of course, back before the site even

Why it failed

I took this directly from a newspost on what.cd, and I have no association with anything written here. Just thought HN would find it interesting. What.CD is a private tracker. Thus, the entire site, staff, and community all revolve around a common piece of software - the tracker

Kind
startup
Status
Shut down
Inventor
Goonbaggins
Ended
2010
Source
hackernews
View original source