Speed optimisations #1

merged 4 commits into from Aug 5, 2011


None yet
2 participants

lozzd commented Aug 3, 2011

Gets file transfer down from 15 minutes to 3 minutes for 6/12 nodes and a 4.5GB file.

Removing rate limits etc should be pretty safe; even with SSD this wasn't anywhere near maxing out a gigabit interface on any one host.

lozzd added some commits Aug 3, 2011

@lozzd lozzd Remove the fairness rate limiting, all hosts can have as much data as…
… they want when they request it. Removes the CPU bottleneck on transfers. Before this, we were CPU bound on a single CPU core due to excessive string manipulation
@lozzd lozzd Backported fix from released BitTornado ccf3b3c
@lozzd lozzd Tweak the default config paramters A LOT. If you have a dedicated gig…
…abit network, you certainly don't want to limit to 10mb/sec. Up the download slice size; maybe this won't be the optimal for you, but we tested with 8kb to 1MB slice sizes and this was by far the fastest. Allow more uploads.
@lozzd lozzd Pass a parameter to BitTornado to set the piece size to 0. This enabl…
…es automatic piece size calculating to enable the most optimal piece size for each torrent. Having tiny piece sizes for a 7gb torrent makes no sense.

russss merged commit bcce1a2 into russss:master Aug 5, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment