Bug 338520 - Add more peers to the high priority chunk downloads
Summary: Add more peers to the high priority chunk downloads
Status: RESOLVED WORKSFORME
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: 22.08.3
Platform: Gentoo Packages Linux
: NOR minor
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-24 11:16 UTC by ZyX
Modified: 2023-01-28 22:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ZyX 2014-08-24 11:16:13 UTC
When downloading some file in the torrent with high priority (using “File Download Order” plugin) I constantly see the following situation:

1. At the very beginning priority is ignored completely (ref https://bugs.kde.org/show_bug.cgi?id=307280).
2. When all previews were downloaded and download of the file that currently has the highest priority is almost finished downloading of this file almost stops: some remaining chunks are being downloaded with low speed peers, but all high speed peers are assigned to the remaining files. This may lead to a ridiculous situation where you have files 1 and 2 at 97% and files 3, 4 quickly raising to 100% complete (likely stopping at the same 97% for the same reason), and 1 here has highest priority, 2 has normal and 3, 4 have both lowest priority.

I suggest that all peers that can be assigned to the chunks belonging to the file with highest priority should be assigned to these chunks (i.e. increase the number of peers that simultaneously upload remaining chunks until these chunks are finally not downloaded).
Comment 1 Andrew Crouthamel 2018-11-12 02:58: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 2 Andrew Crouthamel 2018-11-21 04:36:21 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 3 Justin Zobel 2023-01-10 01:51:57 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 4 Bug Janitor Service 2023-01-25 05:06:27 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!