Penalise those who set uploads to ludicrously low speeds

[Data]

I'm totally new to Bitcomet and as such I don't know if this is even an issue and if it is, whether there is any viable way to combat it.

Does Bitcomet allow situations where users can set their upload speeds to such stupidly low values that they become a detriment to the quality of the Bitcomet sharing system? If so, are there no viable methods that the Bitcomet authors can programmatically implement into the Bitcomet client to penalise these chumps who set their upload speeds to very low settings compared to their download speeds? Maybe cripple their own download speeds until they set a ratio for upload that is acceptable, an maybe even prevent 100% completion of a download until their U/L Ratio is an acceptable level?

It's extremely annoying seeing my KB/s Up figure going at 25k while my KBs/dn is crawling along at 5k. I'm also wondering at the information shown in the Peers information screens. I can see clients that are showing between 30 - 300kb in the KBs/ peer dn column, are apparently downloading from my client and yet my KBs/dn from that client shows 0kbs. I'm also confused that when I add up the KBs figures in the KBs/Up column, it always comes to around 10 Kbs less than what is showing on the main page showing the files I have listed for download.

I'm also not sure how to interpret client listings that show high speeds such as 100KBs in the KBs/ Peer DN column and yet they neither are downloading from me nor I downloading from them. Just whhere are these clients downloading from and uploading to in these cases?

Or am I mis-reading everything in this Peer information page :)

[The UnUsual Suspect]

Hi,

Bit torrent protocall already sends the most download data to those who upload the most.

Therefore, this is not an issue, as anyone who restricts their upload will get very slow download.

However, the biggest problem facing bit torrent is the following...

Some users get slow speeds, so instead of taking the time to learn how bit torrent works, and improve their speed, they figure they will just download ten torrents at the same time.

Now all of their torrents are extremely slow, but they feel good about it, cause they are getting several at the same time (we even had one member here running over 100 at the same time).

The problem is that you are connected to hundreds (or possibly thousands) of peers, and your not providing any worthwile upload to any of them. In fact, all you are doing is harming anyone you connect to.

If it was upto me, I would make the clients not allow a second torrent to run until your upload reaches a certain level in the running torrent.

I can download (and fully seed) several movies in one 24hour period running them one at a time, so I see no poiint in running multiple torrent, and I will never seed a torrent when I can only provide one or two kB/s to it, that is just not polite.

Suspect

[Data]

As a new user I wasn't aware that your download speeds will be slower if your upload speed settings are low. That's one reason for people not to have low upload speeds. Neither was I aware that setting your max connections high can cause issues. The FAQ doesn't mention important things like this as far as I could tell.

Maybe there's a need for another specific FAQ that higlights settings that can be detrimental both to the end user's client experience as well as the overall performance of the system for everyone else? Having performance info in one place rather than scattered across various posts and general FAQ sections will ensure it's not missed by anyone looking to get the best experience with Bitcomet?

I hope my settings are fine. I have 4Mb cable modem with download speeds of around 3700 Kbits/s and uploads of between 300-350 Kbits/s. I have my d/load speed setting at 360 Kbytes/s and upload at 27 Kbytes/s, with max connections at 3. Does this sound optimal?

Thanks for the info.

Edited November 6, 2006 by Dark_Shroud (see edit history)

[bitdave]

Maybe there's a need for another specific FAQ that higlights settings that can be detrimental both to the end user's client experience as well as the overall performance of the system

Have you seen our Settings Guide(link in my sig).

I think it covers everything you're looking for.

If not please PM me with what info should be included in it.

[The UnUsual Suspect]

We do have a couple very good settings guides posted, which I recommend you go through, rather then just advising you on a couple areas in a forum post.

One important setting is your max upload speed. If all of your bandwidth is used to upload data, you will become unable to respond to requests for data fast enough, therefore you will get bypassed, and your download speeds will suffer.

So basically, more upload means more download, but running your uploads unlimited will bog down your client, which will reduce your download speed.

The key is to find the right settings that work for your connection. A good place to start is about 80% of your max upload speed. This will allow enough bandwidth to send and receive requests for data, and respond.

You can then remove your max upload speed limit when seeding.

Suspect

[kluelos]

Bittorrent clients use a so-called "greedy" behaviour to decide which peers to connect to. They seek out and maintain the fastest and most reliable connections they can find in the peer list. But all connections are mutual agreements.

If one peer is set to (or just has) a very low upload speed, other peers will prefer some other connection if they can. This means that the problem tends to solve itself. That person may be seeding, but nobody will connect to him for very long, just enough to find out that he's so slow and there are better connections available. That guy can seed for a couple of days and find that he still hasn't uploaded very much, since nobody wants to put up with his slow speed.

For leeching, clients are forced to trade. They trade with the best partners (and again, that's a mutual thing). If you set your client to upload nothing, your download will become painfully slow because you have nothing to offer in trade or don't deliver what you said you would. All you'll get is the occasional "trial" from somebody seeing if you're still choked. Then they'll decide that you are, so they'll go back to ignoring you.

[silverl]

How can we find out if that person may be seeding but uploading is so very slow by looking at the screen and how to ingor him/her?

Is there a setting where BC wouldl connect to peers that is uplaoading at a fairly acceptable speed?

Edited November 6, 2006 by Dark_Shroud (see edit history)

[kluelos]

There is no point to quoting the entirety of the post just above yours.

The problem of slow uploads pretty much solves itself, and bittorrent clients manage their own network connections better than this can be done manually. The client is constantly watching and adjusting to network changes, while you're just seeing a momentary snapshot of conditions. They guy you think is too slow, somebody else might think is their best source. So let it manage its own network, and it will self-optimize to the best that can be done currently.

[Sapphrina]

So what you are saying is that if I have uploads that are faster than my dl and the people that I am connected to or vice-versa that have 0 upload, that is ok even though I am uploading and they apparently are not?

:blink: Sapph

[The UnUsual Suspect]

You have to look at the entire swarm, just because you arn't getting data directly from a peer your sending data to, doesn't mean he is not uploading.

In fact, that peer could be the biggest uploader of all connected peers.

What Kluelos is saying is bit torrent protocall knows what ALL the peers are doing, and you can only see a small fraction of this.

The only thing you need to concern yourself with is finding the best settings so you can send as much upload as possible, and still have enough bandwidth left to reposond to requests quickly.

Let the swarm punish the leeches, and reward the uploaders, as it is intended to do.

Suspect

[Sapphrina]

[ ;) Tks