-
Notifications
You must be signed in to change notification settings - Fork 445
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
[7.5.0RC6] Channels screen uses 75% CPU #5377
Comments
I always knew the way I implemented the "waiting" animation is gonna bite us in the back... It was not that bad until a lot of channels were added. |
OK, thank you for that insight. Removing the spinning animation really degrades the experience that Tribler is working hard for you. Let's think.. |
AFAIK, that's not trivial, especially with custom-drawn table delegates. There is no light-weight support for icon animations in QT. The corresponding Stack page describes the simplest solution that connects the animation redraw signal to redraw the whole table along with more sophisticated ones. To solve this, I'll have to try 3-5 different methods and it is entirely possible that this can't be solved without going to higher-lever APIs like QML, or going lower with e.g. platform-specific API calls, etc. For now, I would just disable the animation completely. |
Installed RC6 on Ubuntu 18.04 LTS.
When running Tribler idle for 7 hours it uses 5 hours and 11 minutes of CPU time.
The "discovered" screen seems to use a lot of CPU when refreshing. Discovered 1957 channels and subscribed to 26 channels.
4.4G Jun 15 17:19 metadata.db
.Dramatic drop in CPU when moving away. The laptop fan turns off when switching to the "Downloads" screen, reproducible. Note that the CPU usage debug panel graph in Tribler itself is not accurate, it misses the CPU usage. Not a showstopper, but hopefully something we can fix without too much efforts.
![Screenshot from 2020-06-15 17-12-30](https://user-images.githubusercontent.com/325224/84674963-e80f6900-af2b-11ea-89b5-6c16d26effe9.png)
btw To discuss: this is the sort of manual testing I hope we can Devops / automate in the coming months with a single Dashboard approach.
The text was updated successfully, but these errors were encountered: