Uploading limited to 15?

[Passion4diving]

No matter how many torrents I have active (even one), the uploads are limited to 15. I have plenty of excess bandwidth, so I do not think that is the problem. The ones that are waiting say that I am interested but choked. Any ideas as to what is causing the choke? This was the situation since I started using Transmission at 1.41. Now I am using 1.51 (8040) and the limit of 15 remains. I joust want to seed to more folks so that is the reason for my question.

Apologies if this has been answered (searched but came up with nothing) as I am a newbie on this forum. If there is an answer or a way to increase the number of uploads, please provide the URL.

Thanks

[livings124]

Have you checked the bandwidth preferences to make sure upload isn't limited to 15? What about the inspector -> options.

[Passion4diving]

As a Mac user

In the Transmission preferences:
Under peers:
Maximum connections: 400 peers
Maximum connection for new transfers:160 (whatever 'new transfers' means)

Under bandwidth:
Global up: 95KB/sec
Global down: 85

Speed limit mode:
Global up: 350KB
Global down: 500KB

Under transfer management:
Global seeding ratio: 4.0
Queues:
Download with maximum active transfers: 100
Seeding with maximum active transfers: 200

I can find no setting in the inspector -> options (which is set for each torrent) that limits the number of seed uploading

As I mentioned, not matter how many torrents I have active, the upload seeding is always capped at 15. Even one torrent shows this cap.

I have plenty of bandwidth (generally over 1.74MByte down and 550MByte up), so that is not the limiting factor.

I can find no option that caps uploading to 15 seeds.
The waiting seeding requestors show that I am "interested and choked" but as I mentioned, I can believe that bandwidth is not the problem.
Sometimes there are dozens of waiting seeds wanting an upload.

So what is causing the choke?

Is it a cap within the Transmission application?

Any ideas?

[livings124]

Sounds like your ISP might be capping you.

[Passion4diving]

But how would Cablevision know which IP address is associated with which torrent? When I have 5 torrents running, the upload is still capped at 15 each. So how would CV know?

[Passion4diving]

Any other ideas? Anyone? Really not a problem, just want to seed to more folks.

[guilherme]

You mean that when you're seeding you can't seed to more than 15 peers or that you can't seed faster than 15 KB/s?
If it's the former, there's a ticket to implement uploading slots on 1.60 (I *think*).

I'm also under the impression that I can only seed to 15 peers per torrent, which is a nice number for my 600 Kbps up connection.

[Passion4diving]

To be clear, the torrents are capped at 15 uploading peers per torrent no matter how many torrents I have active. Bandwidth varies widely among those that are uploading; have seen some at 140kB/sec.

It is the number of peers that is capped; those waiting say that I am "interested and choked."

Strange.

Cannot see how my ISP is involved as they do not know how many torrents I have running (or even IF I have torrents running as I use encoded connections and change my port frequently).

Once I paused a torrent that was just uploading, as I have finished the download. Upon restarting, the peers wanting to upload appeared immediately. My upload count went to 17 peers and then just as quickly dropped to 15 peers and remained so.

I still think this situation is somehow within the Transmission app. I can find no options in preferences nor in the Inspector that seems to control this cap on uploading peers.

Maybe some experts can guide me to look at something else (I hope you can). I am using the -n version of Airport (recently upgraded with newer firmware) and a cable modem via Cablevision. I am on 10.5.6 of the OS.

Really, all I am trying to do is be a "better" torrent citizen and upload to more peers. I have the bandwidth that is going unused. Isn't that a good thing to want to do?

PS: speedtest.net informs met that I generally achieve some 1400kb/s (or 175kB/s) on uploading between NYC and San Francisco.

[essiw]

I also have that (not that I mind, I only have 40KB/s upload) while uploading: 15 of 125 connected (strange I am sure my peer limit for torrents is 100... an other bug?)

[livings124]

Whoops, I read that as upload SPEED being capped to 15. Yes, there seems to currently be a limit to 15 seeds to upload to.

[Passion4diving]

That is sooo good to read.

I have spent hours trying to debug any possible network issues. Scratching my brain as to how my ISP/Airport/Modem/network setting/network flow/OSx internals could have caused this cap on the number of uploading peers. Was like my college days pulling all-nighters. Only my cats were happy, being nocturnal creatures and getting pets when the house was normally dark and quiet.

Then I find out it was my poor wording. And to think I earned my living as published computer systems researcher/analysts/designer. Must of lost everything once retired.

[Robby]

<snip>Must of lost everything once retired.

[Passion4diving]

So is this cap of 15 uploading peers something that is permanently build into Transmission? Are there plans to make this cap adjustable in the future?

Just want to upload to more peers.

[atomsk]

i can confirm this. It affects Mac OS only.

The MacOS gui uses plists for configuration. In Controller.m in method init it feeds those values from the plists to the tr_bencDictAdd* functions.
TR_PREFS_KEY_UPLOAD_SLOTS_PER_TORRENT is not set there, so on Mac, upload slots per torrent is hardcoded to the default 15 (or 14?).

By adding this line in Controller.m:

Code: Select all

tr_bencDictAddInt(&settings, TR_PREFS_KEY_UPLOAD_SLOTS_PER_TORRENT, [fDefaults integerForKey: @"UploadSlotsPerTorrent"]);

and by adding UploadSlotsPerTorrent to the Defaults.plist i was able to raise it. But im back to using the 2.13 release. The current nightly build was slower and showd me the beachball of death a little too often, even in the release configuration.

I couldnt figure out how to get the project over svn. I would try and write a patch and add this to the preferences window.