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

Tribler becomes unresponsive with a large tags.db #7053

Closed
devos50 opened this issue Sep 19, 2022 · 1 comment · Fixed by #7062
Closed

Tribler becomes unresponsive with a large tags.db #7053

devos50 opened this issue Sep 19, 2022 · 1 comment · Fixed by #7062
Assignees
Milestone

Comments

@devos50
Copy link
Contributor

devos50 commented Sep 19, 2022

Describe the bug
When using Tribler with a large tags.db (mine is 4.58 GB), Tribler becomes unresponsive fast, and everything blocks when doing searches/browsing through channels.

To Reproduce
Steps to reproduce the behavior:

  1. Search for some content, like 'ubuntu' and scroll down. I noticed that the first request to /search completes pretty fast, but scrolling down in the list of search results and loading the subsequent batches is very slow and blocks the Tribler core entirely.

Expected behavior
Tribler should remain responsive with a large tags.db.

Desktop (please complete the following information):

  • OS: macOS Monterey 12.3
  • Tribler's version [e.g. 7.10.0]: latest commit on main branch.
@devos50
Copy link
Contributor Author

devos50 commented Sep 19, 2022

I managed to track down the performance bottleneck to the get_tags_operations_for_gossip method. Returning [] from this call to sidestep the database query makes Tribler responsive again.

@drew2a drew2a self-assigned this Sep 19, 2022
@drew2a drew2a added this to the 7.13.0 milestone Sep 19, 2022
@drew2a drew2a mentioned this issue Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants