Thread: how to set up rtorrent for 1gbps shated seedbox ?

I seach google but coudlnt find anything for 1ggbps for r torrent




is there anytrhing or anyone can help me set up correctly my rtorrent for 1gbps my upload speed always >30mb/s but I couldnt see more than 8-10 mb/s from rtorrent why ? even my cpus is%20 ıor less how you guys set up ? I seen many people upload 100mb/s from rtorrent


thanks

Between how many users is the 1Gbits connection link of the server shared? (how many users / server?) If there are 8 people on the server it's nearly impossible to get higher upload speeds than 30-40MB/s.
The extremely high uploadspeeds are nearly always achieved with Deluge as bittorrent client.

Do you use autodl-irssi to get the torrents as fast as possible? What kind of trackers are you using? (The highest speeds or achieved on 50GB+ torrents on the SCC Archive)

If you have checked those things please post your rutorent/rtorrent settings, because it's pretty hard to help you without any further information.

8 people on server 2 peopel on HDD on evobox I never seen more than 8mb an in genereal its 3-4 mb/s

I use RSS because my main tracker doesnt support autodl-irssi its hd-torrent I use it for true HD all torrents size between 20-50 gb sometimes tv series season can be 150 gb



this is rtorent.rc

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
#max_peers_seed = 50

# Maximum number of simultanious uploads per torrent.
#max_uploads = 15

# Global upload and download rate in KiB. "0" for unlimited.
#download_rate = 0
#upload_rate = 0

# Default directory to save the downloaded torrents.
#directory = ./

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
#session = ./session

# Watch a directory for new torrents, and stop those that have been
# deleted.
#schedule = watch_directory,5,5,load_start=./watch/*.torrent
#schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low.
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,"stop_on_ratio=200,200M,2000"

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
#port_range = 6890-6999

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whetever the client should try to connect to UDP trackers.
#use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
# encryption = allow_incoming,enable_retry,prefer_plaintext

# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
#
# dht = auto

# UDP port to use for DHT.
#
# dht_port = 6881

# Enable peer exchange (for torrents not marked private)
#
# peer_exchange = yes

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

First of all, don't expect speeds being more than 40MB/s upload(this is already very rare), if it happens it's great, but they will be usually in the 20MB/s range because there are a lot of people on the server.

I would recommend you testing the speeds on a top level tracker where you can actually reach high speeds. I don't think that the swarms on your favorite tracker are that strong. (even new IPT p0rn packs can be used for testing, if you don't have a good tracker).
If you download an 'old', a few hours old, torrent what are the speeds you can reach? This is also an indicator of how strong the swarm is.

Edit the 'rutorrent-files'/plugins/rss/conf.php file. Change the update interval to 1, 5 or 10 minutes(whatever you like, default:30min)

Your rtorrent settings seem fine, but I can post you other ones, with which I have seen great speeds, but I don't think you can expect more on hd-torrent. (I'm not a member there, but I haven't heard many good things about it).

I beg to differ. While rtorrent is not as aggresive as deluge, it can still get speeds of 100+ MB/s. The main problem here is that you are using a shared HDD and you are downloading only torrents which are bigger than 20 GB. Needless to say that if you are downloading a 150 GB file on a shared disk, your speeds will be aweful since the drive will start crawling within 1 minute. Downloading simultaneously 2 or more big files you will get the same result as well.

Shared HDDs are not good for such tasks. You will have to look for a dedicated HDD or limit your active downloads to maximum 1 at a time. When the download starts, you should also stop all other big seeding torrents so that your line doesn't get saturated.

freeman do you think getting on 2gbps Stream from EvoBoxes - Hosting would be better I mean Im raring 100gb per hour I upload 70 mb/s froım rapidshare program but I only seed 4 mb/s from rutorent

Originally Posted by Freeman_

I beg to differ. While rtorrent is not as aggresive as deluge, it can still get speeds of 100+ MB/s. The main problem here is that you are using a shared HDD and you are downloading only torrents which are bigger than 20 GB. Needless to say that if you are downloading a 150 GB file on a shared disk, your speeds will be aweful since the drive will start crawling within 1 minute. Downloading simultaneously 2 or more big files you will get the same result as well.

Shared HDDs are not good for such tasks. You will have to look for a dedicated HDD or limit your active downloads to maximum 1 at a time. When the download starts, you should also stop all other big seeding torrents so that your line doesn't get saturated.

I never said that rtorrent can't reach upload speeds of up to 100MB/s, but it's pretty difficult and certainly not possible with this kind of VPS/seedbox.
I do agree that he should at least get a dedicated HDD and 8 people on a server is a lot.

In this particular case I think that the tracker swarm is also relevant.

EDIT: I think you should either get Current from Evoboxes, a dedicated server and/or a different provider. You can't expect to get such high upload speeds on a server with that many people. I'm using a VPS on a 1GBits sver shared between 3 or 4 people and I'm pretty happy with the speeds.

can you write here adress and I can check ?

Originally Posted by Freeman_

I beg to differ. While rtorrent is not as aggresive as deluge, it can still get speeds of 100+ MB/s... The main problem here is that you are using a shared HDD and you are downloading only torrents which are bigger than 20 GB. Needless to say that if you are downloading a 150 GB file on a shared disk, your speeds will be aweful since the drive will start crawling within 1 minute. Downloading simultaneously 2 or more big files you will get the same result as well.

Shared HDDs are not good for such tasks. You will have to look for a dedicated HDD or limit your active downloads to maximum 1 at a time. When the download starts, you should also stop all other big seeding torrents so that your line doesn't get saturated.

Your points about shared hard drives are right on the money. Having less users, infrequent users or ideally.. own disk will make huge differences as the drive is often the bottleneck in the system. And deluge is a bit more aggressive at pushing connects. But I can only imagine that you are referring to burst speeds when you say that 100+ MB/s is common. If that's what you meant, we agree. But it's uncommon to see sustained speeds above 50 MB/s. Certainly SATA drives won't sustain that rate, you need faster RAID arrays or SSD drives to take full advantage of Gigabyte+ lines. Even with notably fast swarms e.g. large SCC packs.. if you clock the completion times, even the fastest Gigabit boxes in the swarm will rarely exceed an end to end average speed > 40 MB/s.

So while you can see bursts to ~ 100 MB/s, even dedi gigabyte (non SSD) will only 'sustain' ~ 60 MB/s for a portion of the torrent. And the end to end average will be substantially lower than that. You can do better with dedi SSD, but I still wouldn't expect to average anything near 100 MB/s.

I'd love to be proven wrong. So if you know something that we don't, please share!