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

cpu core is constantly at maximum #7790

Closed
kotenok2000 opened this issue Dec 29, 2023 · 8 comments
Closed

cpu core is constantly at maximum #7790

kotenok2000 opened this issue Dec 29, 2023 · 8 comments

Comments

@kotenok2000
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Start running tribler
  2. wait for a day

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: Microsoft Windows [Version 10.0.22631.2861]
  • Tribler's version 7.13.1

Additional context
Add any other context about the problem here.

@synctext
Copy link
Member

Interesting report, thnx!

13.20% of CPU power goes to Trivler.exe... Is that a 16-core or other heavy multicore machine?
Seems also some uploading or anon encrypted relay traffic is going on. Changed the settings? Did you subscribe to many channels possibly?

@kotenok2000
Copy link
Author

I have 8 hyperthreads

@qstokkink
Copy link
Contributor

@xoriole do you think this is related to #7711 (comment) ?

@xoriole
Copy link
Contributor

xoriole commented Jan 2, 2024

@qstokkink #7711 is for the debug pane for the first time opening, it is unclear if the debug pane was open in this case.

@drew2a
Copy link
Contributor

drew2a commented Feb 1, 2024

Channels consume a significant amount of CPU, as does anonymous downloading.
The channels are now retired:

And the CPU usage for anonymous downloads should be improved:

There is a high percentage chance that the problem will be solved in version 7.14.

@kotenok2000
Copy link
Author

Still happens on Tribler_7.14.0-debug_x86
tribler-core-error.log

@drew2a
Copy link
Contributor

drew2a commented Apr 30, 2024

Sorry for the misinformation. The changes I mentioned were intended to be in 7.14 if we had followed the regular release process. Now, they are scheduled for 7.15: https://github.com/Tribler/tribler/milestone/44

@qstokkink
Copy link
Contributor

The mentioned changes are now part of the release branch for version 8.0. This should now be solved for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants