Bug 316905

Summary:	Maximum speed limits does not account for Bittorrent traffic
Product:	[Applications] ktorrent	Reporter:	Dulaurier.f <Dulaurier.f>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	saipg.rigel.alnilam
Priority:	NOR
Version First Reported In:	4.3.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dulaurier.f 2013-03-17 12:43:52 UTC

The upload or download speed limits that can be specified in Ktorrent does not take account of the bandwidth generated by the bittorrent traffic in itself (protocol control, TCP headers, DHT, etc.). This often cause saturation of the bandwidth (mainly upload one) that cause an overall slowdown of the internet connexion (not only in Ktorrent).
Leaving a great margin in the limits is not a good answer to this problem, because the bittorrent control traffic bandwidth varies within great boundaries (1-75 kiB/s) given the number of torrents, peers, DHT, etc., used.


Reproducible: Always

Steps to Reproduce:
1. Set your upload speed limit to nearly the maximum allowed by your connexion
2. Add some torrents with a great number of available peers, so it can generate a lot of BT traffic
3. Compare the upload speed actually showed by KTorrent with the true one (in your router, or NIC)
4. See the great difference there is and the overall download speed falls as there is a lack of upload bandwidth that causes lags in the control traffic
5. Set the upload speed to 10% of your connexion maximum and see the download speed goes up again



Expected Results:  
The speed limits in Ktorrent should be TOTAL traffic limits and not only DATA traffic to reflect reality.

I know that this can be considered as a "feature request", but due to the fact that it causes malfunctions of Ktorrent (and other softwares), it can also be seen as a bug.

Comment 1 dimmer 2013-06-25 05:39:51 UTC

Here the same. Ktorrent exceeds the limits. In GUI shows that holding on to the  uploads limits, but network monitor shows that differently.

DHT off.

Comment 2 Andrew Crouthamel 2018-11-10 03:24:12 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-21 04:42:11 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Justin Zobel 2023-01-12 01:58:10 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2023-01-27 05:07:21 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2023-02-11 03:52:09 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!