help optimising rutorrent

randac56

Member
May 25, 2018
915
0
16
rTorrent and ruTorrent work properly on my seedbox

Now I need to optimise the configuration in order to get the max results.

My box is a semidedicated server (a server divided into 4 VPS)

Every VPS has;
Intel Xeon (1 x 2.8 GHz)
2GB DDR3 RAM
1 x 500GB SATA2 Hard Disk
1Gbit Connection
Unmetered Bandwidth

Don't know what to put in Advanced settings.

Thank you for helping me.
 

peshua19

Member
May 25, 2018
897
0
16
well that's a loaded question...you can do many things...optimize the linux environment and filesystem, you can tweak the .rtorrenr.rc settings...but what exactly are you trying to optimize it FOR....Speed? Memory use?

Also, rtorrent does a fair job of self optimizing if you give it the proper settings....just don't have super expectations....a huge misconception among seedbox buyers is "If i buy a Gb/s box i should get Gb/s speeds"


This isn't ever true. I'd say the average Gb/s seedbiox does around 20 MB/s with a peek of 40-65.


Also, another huge misconceptions is "theres 50 leechers, i should be connecting to them all or i should be connecting to more than 10" This simply isn't true, and never has been true. It boils down to how the bittorrent protocol works.


Bottom line, first be more speciic with your request and then we can help
 

simur612

Member
May 25, 2018
879
0
16
My rtorrent which has abt 20 torrent of total 100GB always crash, there are some big file (> 10GB)
the other rtorrents which running paralel are stilll ok , what s the problem ?
 

peshua19

Member
May 25, 2018
897
0
16
dude, not to be a jerk but how the hell would we know?

That's like saying "my car starts making weird noises when i drive it, what's wrong?"


Without a lot more information how would anyone be able to help?
 

simur612

Member
May 25, 2018
879
0
16
Sory I forgot the log file, will post soon

And can you help me make a script to run all instance of rtorrent every hour (in case someone crash it can be restore) like this: (I made the start up script as Subsy's tut )

sudo /etc/init.d/rtorrent start
sudo /etc/init.d/rtorrent2 start
sudo /etc/init.d/rtorrent3 start
sudo /etc/init.d/rtorrent4 start
sudo /etc/init.d/rtorrent5 start


I tried with Webmin crônjob but it does not run
 

peshua19

Member
May 25, 2018
897
0
16
no, instead use cron. i already posted a script in this forum which will work for this, and you can set cron to run as often as you like (even every 5 minutes)


use the search option.
 

randac56

Member
May 25, 2018
915
0
16
My problems are the slow speed and the use of ram:




This is my .rtorrent.rc
Code:
scgi_port = 127.0.0.1:5000

# 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 = /home/admin/downloads

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

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/home/admin/torrents/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.
 

lisas4567

Member
May 25, 2018
773
0
16
smiley.gif
lo m8,

It seems that you have not set some basic parameters for rtorrent eg. mas upload and down speeds, peers etc etc.

Is this actually your rtorrent.rc?

PS what wonslung suggests about using his cron script for checking whether rtorrent is running works a treat wink.gif
 

peshua19

Member
May 25, 2018
897
0
16
your speeds don't look slow to me. The look fine.

the "use of ram" as you call it, is probably not being reported correctly. The cpuload plugin isn't great. For "actual" reporting, use shell program like "top"
 

peshua19

Member
May 25, 2018
897
0
16
yah, i dind't mean it as an insult. I just mean that sometimes it's wrong, ESPECIALLY if you're not on linux (FreeBSD, OpenBSD, Solaris, OpenSolaris)


For instance, right now, it's reporting 51% cpu use on one of my systems.

When i check this system in top i see this:
Code:
CPU states: 93.9% idle, 1.8% user, 4.4% kernel, 0.0% iowait, 0.0% swap
 

lisas4567

Member
May 25, 2018
773
0
16
Agreed, the load plugin is like a ruff idea of what's going on. What does top show for ya? I had a feral giga slice and i had the cpuload showing at 100% for a while when i ran top on the server. I could see that someones rtorrent had locked up and was maxing out on cpu usage. Well i just assumed he was doing a crap load and was hogging cpu. When i complained, staff said rtorrent had locked up. When the restarted it, everything went back to normal smiley.gif