2009-12-09 09:21:24 PST
Actually, it was the fault of trickle. I don't know why it would force an app to consume so much memory while shaping it. I've also seen a similar behavior while shaping xbt but this time using tc htb egress shaping only.
No, I haven't enabled logging yet. I'm planning to run xbt for a week then do some other testings.
Comparing xbt to opentracker, both have nice things, but opentracker seems to be above it for the following reasons (which I like)
1) it poisons the swarm with random IPs for the purpose of plausible deniability. This is very useful for public trackers and I like that. Tracker operators don't want to play cops for companies that lurk in tracker swarms and then try to sue people just by getting their IPs from there and claiming it is 100% valid information... xbt doesn't have it
2) it accepts custom IPs sent by clients no matter where they are
3) it can restrict stats to a custom IP only so others wouldn't lurk around. Currently, my opentracker gets its stats from 127.0.0.1 so no one is able to get them from there but me.... xbt can't do that
4) doesn't need any DB which is a plus for various reasons, like reduces wear & tear of disk as it doesn't write anything to disk and minimizes possibility of data loss or other problems in case something goes wrong with the DB
5) it supports compressed gzip full scrapes (does xbt support that?)
6) it can sync in a cluster. Though a plus feature, it's not interesting for me
on the other hand, comparing bandwidth of opentracker and xbt, it seems xbt beats it. While running opentracker, it tends to download ~20-30 KB/s and upload ~10-20 KB/s. Switching to xbt, download is ~10-20 (most of the time its ~10-15) KB/s and upload is ~5-15 KB/s. both trackers have an announce and full scrape interval of 45 minutes (2700 secs). This is all on a swarm of ~35000 peers tracking ~4800 torrents