Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion about managing huge amount of torrents, RAM usage #11397

Closed
reyaz006 opened this issue Oct 26, 2019 · 5 comments
Closed

Suggestion about managing huge amount of torrents, RAM usage #11397

reyaz006 opened this issue Oct 26, 2019 · 5 comments

Comments

@reyaz006
Copy link

reyaz006 commented Oct 26, 2019

qBittorrent version and Operating System

4.1.8 x64 / 8.1 x64

What is the problem

  • qBittorrent eats too much RAM and acts unresponsive.
  • It can take dozens of minutes to launch.
  • It can eat up to 8 GB of RAM while recently it was just up to 1.5-2 GB.
  • It launches with the All torrents view by default and since I've noticed it lags when all torrents are displayed I'm always trying to switch to some category to decrease the amount of torrents for qBittorrent to display. It launches minimized and I'm clicking it to bring up its window faster. Sometimes the window displays just blank, apparently unresponsive but I can see that menu works if I click on menu items. In that state, I can click Close [X] and expect it to get minimized to tray again but instead it will terminate and I need to launch qBittorrent again.

What is the expected behavior

  • Smarter memory management.
  • No lags in GUI.

Steps to reproduce

  • Have about 30000 torrents in qBittorrent, most of them in Finished state.
  • Quit and launch it again.

Extra info(if any)

  • I didn't restart qBittorrent for quite a long time and recently decided to install latest OS updates including Meltdown fix. Not sure if it's relevant.

SUGGESTION

Since of course the huge amount of torrents contribute to RAM usage, why not explore more options to make it more effective?
Consider my case: You could suggest me to get rid of most of old torrents but I will not do that. It's because it's basically a database of what I've downloaded during years of using qBittorrent. Some torrents were never started, some finished with only certain files chosen to be downloaded, some I seed again when I want. But absolute most of them are in finished state. I do not need them or most of their properties accessible immediately in my RAM. I only need their metadata like Title and Date added. I'd place them under a special category, e.g. Archive and only go there when I need to lookup certain torrents. Then if I find something I need, I'd check the situation - what files were supposed to be downloaded, what files were skipped but still available, how many seeds and peers are there currently, how much I've already seeded etc. If I just remove the torrents from qBittorrent, all of that metadata would be lost, and worst of all are cases where I did not chose to download all files - if I decide to add a torrent again after I removed it, extra unwanted files may get downloaded.

So basically I propose to implement ability to move a torrent into archive. After a torrent moved to archive, it's stopped completely (whether it was finished or paused) and only its very basic details should be kept in RAM like title and date added (maybe allow more fields to choose in order to be able to sort by them, e.g. size). Not even the done %% is really needed - these details must only get loaded into RAM after the item in archive is clicked. And they should get wiped from RAM after the archive is no longer viewed.

Also, please either fix the RAM usage when "All" group is viewed, or allow to not switch to it by default when qBittorrent is launched.

@reyaz006
Copy link
Author

Something is wrong. RAM consumption increases without stopping and it reached 10GB after a few hours. Upon closing qBittorrent it increased to 12GB then slowly decreased to zero, all while making tons of file operations with swapfile. Previously qBittorrent worked fine for weeks and now I can't let it run for more than 10 hours. If this is not a memory leak, I don't know what is this.

How can I debug this issue?

@xavier2k6
Copy link
Member

@reyaz006 are you still running 4.1.8?

@FranciscoPombal
Copy link
Member

The RAM usage is fixed (#13304 (comment)). GUI performance with many torrents is also being tracked in that ticket.

As for the "archive" suggestion, I'm pretty certain that's a duplicate of a previous issue report, but I can't find it. @thalieht can you find that duplicate, so this can be closed?

@thalieht
Copy link
Contributor

As for the "archive" suggestion, I'm pretty certain that's a duplicate of a previous issue report, but I can't find it. @thalieht can you find that duplicate, so this can be closed?

#11878 and the many others requesting utorrent's "stop" e.g. #948

@FranciscoPombal
Copy link
Member

@thalieht Thanks. Note that the "uTorrent stop issue" is different that the feature request for an "archive" status/category. Closing as the remaining bit of this request is a duplicate of #11878.

@qbittorrent qbittorrent locked as resolved and limited conversation to collaborators Sep 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants