Do not process files from Paused and Completed torrents #13088

New issue

Open

opened 2026-02-21 23:32:34 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 23:32:34 -05:00

Owner

Originally created by @reyaz006 on GitHub (Feb 19, 2022).

Suggestion

If some torrent is in Paused or Completed state, do not process its files in any way. Do not check their existence, do not try to read them. Only do relevant actions when user chooses specific Paused or Completed torrent from the list.

Explanation:
Since there seems to be no interest in implementing #11878, I thought this is a suitable alternative.

Use case

Speed and responsiveness gain from skipping processing Paused or Completed torrents should be great for cases with huge amounts of torrents on the list. Should also optimize RAM and CPU usage.

Extra info/examples/attachments

No response

Originally created by @reyaz006 on GitHub (Feb 19, 2022). ### Suggestion If some torrent is in Paused or Completed state, do not process its files in any way. Do not check their existence, do not try to read them. Only do relevant actions when user chooses specific Paused or Completed torrent from the list. Explanation: Since there seems to be no interest in implementing #11878, I thought this is a suitable alternative. ### Use case Speed and responsiveness gain from skipping processing Paused or Completed torrents should be great for cases with huge amounts of torrents on the list. Should also optimize RAM and CPU usage. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

label

2026-02-21 23:32:34 -05:00

deekerman commented

2026-02-21 23:32:39 -05:00

Author

Owner

@glassez commented on GitHub (Feb 19, 2022):

do not try to read them.

What do you mean exactly? What exactly should it not try to read?

@glassez commented on GitHub (Feb 19, 2022): > do not try to read them. What do you mean exactly? What exactly should it not try to read?

deekerman commented

2026-02-21 23:32:41 -05:00

Author

Owner

@reyaz006 commented on GitHub (Feb 19, 2022):

Files like "archive.zip" and "movie.mp4" referred by "torrent[123456]". Reading "torrent[123456].torrent" is not what I meant to restrict.

@reyaz006 commented on GitHub (Feb 19, 2022): Files like "archive.zip" and "movie.mp4" referred by "torrent[123456]". Reading "torrent[123456].torrent" is not what I meant to restrict.

deekerman commented

2026-02-21 23:32:41 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**