-
Notifications
You must be signed in to change notification settings - Fork 452
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
GigaChannel Community 100% CPU #4636
Comments
Note that this only becomes apparent when the database is really big. |
Would this be solved by #4249 ? |
#4249 will only be a part of the solution. We'll have to start caching some SQL queries (for example, selection of random entries for gossip) and do some other stuff. This is not like finding a bottleneck and fixing it, but more like charting a safe path through a minefield... |
I agree, maybe we should leave this for |
For 7.3 I'm going to address the most offending problems that are relatively simple to fix. |
GigaChannel Community somehow causes up to 100% load on the core and lots of DB i/o. I suspect this is caused by inefficient Pony queries on push-based gossip.
The text was updated successfully, but these errors were encountered: