Small Upload speed after few days

BitComet BitComet Bug Reports
1

I have 2200+ active torrent. All active for upload.

If start BC, upload speed normal, but after few days, upload speed very small (under 100 kb for all). if restart BC, upload speed be normal.

only restart BC. NO restart router (keenetic giga). NO restart PC

other client (Qb) work normal, upload over 61 Tb

ver 1.86 win10x64

 

/monthly_2022_03/1290188920_Image170.png.9aa83f83f5d3686e93f1dc0d04af299f.png" rel="">![](/monthly_2022_03/457100112_Image170.thumb.png.9598e64353e38a89e0698028ab98a536.png)

/monthly_2022_03/605707314_Image171.png.f8edeef262d9aafa71092f67195963be.png" rel="">![](/monthly_2022_03/1933605998_Image171.thumb.png.0c3b2d583d784f482b6db8b1ff9c9822.png)

Image 170.png

Image 171.png

Image 174.png

2

A situation has occurred.

What can be checked? Test?

/monthly_2022_03/1876748382_Image174.png.d37f6485d855b30fac4b07d367cd7213.png" class=“ipsAttachLink ipsAttachLink_image”>

3

Upload speed can be slow for various reasons: Lack of people looking for that file or even your ISP has capped your speed.

What you aren't showing in the screen dump is the number of connections
4

This is a bug with BitComet for a long time. At the low speed point, no matter what you do, BitComet is dead. You just have to restart the BitComet or switch make the painful switch to another torrent software.

5

Check your ports as you may be inadvertently throttling the stream

However, as I said earlier, upload speed depends on how fast a leecher is downloading. If they are slow, then your upload speed will also be slow.
6

This is a problem for quite some time now since version 1.73. Upload speed suddenly drops close to zero but some time later it picks up again, only to repeat the cycle later on once more and continues in this oscillating fashion. This is not a problem with too few leechers being unable to download fast enough, because the same leechers are there all the time.

It seems to be a problem that appears when there is a great number of active torrents ready for upload at the same time. If the number of active torrents to be uploaded is reduced to 100 or less there is no problem at all. It seems that there is a saturation limit reached when there are too many upload tasks, that causes BC to stop sending data even with plenty of leechers connected and waiting to download. It seems as though it enters an Anti-leech mode of operation.

I tried in Options/BitTorrent to Disable the Anti-leech and Protocol Encryption options but this made no difference at all. Also in the Options/Task seeding rules I have this box unchecked. The minimum and maximum upload speeds are set to the "unlimited" defaults. I have also set the Listening Port to be randomized after every start, with all three port mappings that follow be selected.

It would be nice to have some kind of debugging tool to monitor what BC "thinks" when it begins to restrict upload speed. For instance to have some kind of visual notification when the Anti-leech operation has kicked into action or when BC intentionally restricts upload speed. Such information could potentially also appear in the Task Log or Global Log Tab.
7

Hi all,

I have filed a new bug here that may be the root cause of this.

/topic/12820447-large-pending-connections-bug/?do=embed" style=“height:394px;max-width:502px;”>