Earlier this week I noticed that the BitTorrent tracker of Tasvideos is starting to reach noticeable CPU load levels. It is the standard BitTorrent tracker with only minor changes (doesn't forget obsolete movies, remembers useragents).
So I wrote my own.
http://bisqwit.iki.fi/source/bqtrack.html
This tracker was written with two goals in mind:
-- Compatible with the site code (including the way the "dstate" file is loaded and saved)
-- It is as fast as possible.
In particular, I couldn't care less about the http administration/statistics features, which seem to be what most other trackers seem to concentrate at.
I think I accomplished both goals suitably well. However, it has less features than the standard BitTorrent tracker. In particular, it has no NAT detection schemes whatsoever. I don't know how much that matters.
It has also been observed, that it reports significantly higher swarm member counts than the old tracker did -- likely somehow inflated. I have a theory why it could happen (doesn't detect abruptly dropped peers except from a timeout of 1 hour), but I don't know how the standard tracker avoids it.
Also, it occassionally dies from a "too many open file descriptors" error. I don't know how to effeciently avoid that either. (No, it does not leak resources.)
The tracker comes with General Public License, so if someone wants to try a hand at improving it, patches are welcome :)