Page: 1 2 3 4 5 6
You may have noticed a version number was skipped; that's because part of the last release was broken, and I found out quickly but figured I'd better test things before shipping a new one.
T-0.3.6 introduces some very important changes. The first one is a change to port selection as discussed. IF YOU CURRENTLY HAVE PORTS FORWARDED, YOU MAY NEED TO CHANGE YOUR PORT RANGE AND/OR FIREWALL SETTINGS TO ACCOMMODATE THIS CHANGE. Another change is an attempt to fix problems with excessive RAM usage, as discussed . With luck, this will reduce the extreme memory fragmentation we've been seeing.
The last major change is an experimental automatic upstream limiter, which is now the default upload mode for clients. It is NOT perfect, and setting one's upstream manually will work better; but it will allow newbies to receive reasonable download rates without their having to come to the forum and bug people about how to set the download rate.
New version out. This is mainly for fixing bugs; don't know if it'll be a stable release, but if not it's close...
Thanks to everyone who's been reporting bugs and helping me squash them.
A new version of BitTornado has been released. This version includes the smarter upload-rate calculation system noted in the prior message, some changes to hopefully reduce the amount of RAM Python allocates for itself, and various bugfixes throughout the code. Enjoy!
A new function has been added to the codebase, and will be available in the next major release (T-0.3.3); smart upload rate fudging. Like many of my improvements, most people won't even notice it.
What is this feature? It accounts for "TCP ACK" overhead. Basically, when you download, your system sends acknowledgements for the data it's received back up the pipe. This isn't performed at the BitTorrent protocol level, but on a much lower level and the old codebase didn't take it into account. As a result, for people on asymmetric connections with 8X as fast downstream as up (1M/128K for example) or higher, setting your upload at 80% of your pipe's max would still result in upstream flooding at full download.
So what does this change? You will notice that your upload decreases a bit when you are downloading at full speed.
With the new client, it will be recommended you set your upload at 90% or higher of your pipe's max. This will mean better performance on start-up and when downloading without choking your upstream.