No issue downloading with rtorrent, but it’s another story when it comes to seeding, which never seemed to really work well for me under Linux, compared to Vuze on Windows (some time ago).
a number of possible causes including
Vuze works differently than any other torrent client in many ways so comparisons to other torrent clients may not be especially useful.
ISPs often block or restrict the torrent protocol today, so unless you run your tests on the same Internet connection your results may not be valid.
I do also recommend trying another torrent client or two for simple and easy testing, the circumstantial results can be helpful.
why don’t you use vuze? I do use it in 12.2 and I have no issue with it. Did you install it? if you need help with it I can help you and let you know how is configured on my desktop.
The machine in question runs opensuse 11.4 x86_64, with latest updates or so.
Patience seems to have solved my problem. After several hours of wait it started uploading reasonably. I’ve read elsewhere that this client can be slow to start. It could be that in the past the session did not last long enough to pick me on the network.
I am sorry if I have offended you. I meant to say: “I observed different results on another OS, while under the same network, router, ISP, etc.”, which I believe to be useful information to rule out hardware issues. I guess you see this as an attempt to benchmark and compare the merits of the two OSes. Well, I don’t care how well/bad Windows does as such, because I freed myself from it since quite some time (except to occasionnally do very unproductive stuff).
Vuze: So it works now? That’s good news. A few years ago I tried hard to get it to work on opensuse 11.1, but it kept crashing, so I completely forgot about this option.
Why not vuze? I sought a simple enough console client, which I could then turn into a daemon to start on boot.
Hold on… I just saw there is a console UI for vuze too. I will try that for sure in the future.
It is what I suspected. There must be a reason why I was so unhappy of not getting Vuze when I switched to Linux.
> The machine in question runs opensuse 11.4 x86_64, with latest updates
> or so.
>
> Patience seems to have solved my problem. After several hours of wait
> it started uploading reasonably. I’ve read elsewhere that this client
> can be slow to start. It could be that in the past the session did not
> last long enough to pick me on the network.
I also use Vuze on 11.4 and I’ve seen long waits - hours on some releases -
for the tracker to identify peers. There also seems to be many fewer
available connections - right now, my seed for 12.3 RC2 i586 shows 2 peers
available to upload to, for example. So far, my ISP hasn’t messed with the
transfer speed but the bittorrent population appears to be dwindling so I
don’t get too excited if it takes a while.
I did not see it as an offence. Sorry when I gave that impression. Everybody should use what works. But there are sometimes people here that simply say things like: “what is the Linux equivalent of this and this on Windows”. Which simply means nothing to me. A more technical description on what can be done on another OS, so that LInux users can understand what it is in general IT terms would be then be more informative. LIke your above remark that means about: “I can use Torrent on another OS (Windows), including seeding (which imho proves that router, ISP, etc, allow it), but on openSUSE …”
On 2013-03-04 09:36, hcvv wrote:
> I did not see it as an offence. Sorry when I gave that impression.
> Everybody should use what works. But there are sometimes people here
> that simply say things like: “what is the Linux equivalent of this and
> this on Windows”. Which simply means nothing to me. A more technical
> description on what can be done on another OS, so that LInux users can
> understand what it is in general IT terms would be then be more
> informative. LIke your above remark that means about: “I can use Torrent
> on another OS (Windows), including seeding (which imho proves that
> router, ISP, etc, allow it), but on openSUSE …”
I don’t normally use torrent. But when I did try it years ago I think I
had to open ports in the firewall and direct them to my machine - and
these ports can be different on different clients. This is specially
important for seeding.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Unless you own and manage your own Tracker (not that hard to do), If your torrentfile is private, in fact you should run your own tracker and not use a Public Tracker.
There are a multitude of reasons why your seeding may start off slow. In fact, unless you are able to advertise your node as a Super Seeder, it should be <typical> that your connections might not start for up to 30 min. Same could be true for ordinarily client connections, again if you don’t have non-tracker options like Peer and DHT enabled or the other clients don’t have those options enabled.
I’m not too familiar with DHT and how to get it properly started and
working under rtorrent. One thing I did is to open a UDP port in suse
and router’s firewalls. But I did notice a peer_exchange option.
Switching it on might have helped.
One thing that intrigues me: if I move the completed files to an SSD
drive, would it affect seeding performance anyhow? Of course, the upload
speeds are far below the HDD’s speed limit, but an SSD has a way smaller
seek time.
On 03/04/2013 12:06 AM, vazhavandan wrote:
> 11.4 has gone out of fashion
Sure. My everyday computer is on 12.2. It is well and salutes you. This
other machine retains 11.4 for the moment, as I don’t use it much. It
got evergreened.
On 03/04/2013 03:36 AM, hcvv wrote:
> I did not see it as an offence. Sorry when I gave that impression.
This is understandable, with obnoxious brats giving what could be seen
as ultimatums on various forums, which boils down to:
“I had x on Windows. How come not on Linux!? Solve my problem. You have
24 hours. Otherwise… I shall boot Windows, erase Linux, and say
bad things about it to all my friends. gniahahaha!”
Peer exchange <might> help, but how effective depends on a lot of vagaries. Same with DHT, both perform similar functions, allowing each Peer to perform as a mini-Tracker so if the main Tracker is unreachable the peers by themselves can exchange enough info to start exchanging.
Placing on an SSD will not improve performance. Disk subsystems are in another universe of speed compared to networking.
There are an unlimited number of possible causes for slow starts ranging from recognizable networking issues to simply how the application “works.” Today’s torrent clients commonly apply weights on availability, reliability and more. If your machine appear brand new and especially without anything to offer you often start at the bottom of the list of priorities. Prhaps the most common issue is that clients typically don’t re-check the Tracker for updates except at 20 min intervals or so, so even if you are up and registered with the Tracker, it may be another 20 minutes or so before a specific peer will get the info your new node exists.