-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Speed up the startup speed when qBittorent client has several thousands of torrents #646
Comments
I have been experimenting with this the last few days. I may come up with a patch next week. |
I try this: I save all fastresume files into a file just call resume.fastresume. |
addtion, in the readAlerts() >> save_resume_data_alert, i also save the torrent fastresumedata into resume.fastresume file just like you. |
Since you are able to code, I will explain tomorrow a little more how things work in qbt code so you can understand more the code logic. Also I will share with you what I had in mind, for this issue. If you would like, you can implement it then. My thoughts on your monolithic resume.fastresume approach: I don't think it is elegant and not very functional. I also don't like persistentdata file either so I have proposed this already: #583 |
Yeah, you are right, I find my solution works well only when qBittorent quit (It can quit very fast), but when it startups, it just like before. |
These days I just did some work to speed up the startup speed, then i found that maybe the updateTorrentNumbers() -> transferList->getSourceModel()->getTorrentStatusReport() |
Issue is too old. Many performance improvements have been made since. Submit a new issue if needed. |
No description provided.
The text was updated successfully, but these errors were encountered: