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

Keyword search performance and RemoteQuery community #5208

Closed
ichorid opened this issue Mar 16, 2020 · 3 comments
Closed

Keyword search performance and RemoteQuery community #5208

ichorid opened this issue Mar 16, 2020 · 3 comments
Assignees

Comments

@ichorid
Copy link
Contributor

ichorid commented Mar 16, 2020

Currently, RemoteQuery Community does not cache any remote requests. Caching typical requests like queries for subscribed channels should help with database performance.

@triblerteam
Copy link
Member

Could you please post a performance analysis of expensive queries? I prefer to keep Tribler code as simple as possible.

@synctext
Copy link
Member

synctext commented Jun 14, 2020

Adding performance results here for keyword search: 8 seconds in some cases. In other cases it is a snappy fast sub-second result. Something is seemingly blocking in some corner cases. Or the database is simply 4.4 GByte big 👍
Search_duration_Tribler7 5 0RC6
Ubuntu 18.04 with 7.5.0RC6 and 1953 discovered channels.

-rw-r--r-- 1 pouwelse pouwelse 4.4G Jun 14 14:07 metadata.db
-rw-r--r-- 1 pouwelse pouwelse 273M Feb 12  2019 dispersy.db
-rw-r--r-- 1 pouwelse pouwelse 335M Jan 15 12:37 noodle.db
-rw-r--r-- 1 pouwelse pouwelse 400M Feb 12  2019 tribler.sdb
-rw-r--r-- 1 pouwelse pouwelse 342M Jun 14 14:03 trustchain.db

ToDo: investigate, conduct profiling , and add to performance dashboard of Tribler #4999. Not suggesting a fix..! If we know how much development time a likely fix costs, then we can make an informed decision.

@synctext synctext changed the title Cache remote queries for Channels Keyword search performance and RemoteQuery community Jun 14, 2020
@drew2a drew2a modified the milestones: Next-next release, Backlog Sep 15, 2021
@ichorid
Copy link
Contributor Author

ichorid commented Sep 28, 2021

@kozlovsky solved most of DB performance problems! Thank, you Alexander! 👍

@ichorid ichorid closed this as completed Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants