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

GigaChannel Community 100% CPU #4636

Closed
ichorid opened this issue Jun 26, 2019 · 6 comments · Fixed by #4648
Closed

GigaChannel Community 100% CPU #4636

ichorid opened this issue Jun 26, 2019 · 6 comments · Fixed by #4648
Assignees

Comments

@ichorid
Copy link
Contributor

ichorid commented Jun 26, 2019

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.

@ichorid ichorid added this to the V7.3: Gigachannels milestone Jun 26, 2019
@ichorid ichorid self-assigned this Jun 26, 2019
@ichorid
Copy link
Contributor Author

ichorid commented Jun 26, 2019

Note that this only becomes apparent when the database is really big.

@qstokkink
Copy link
Contributor

Would this be solved by #4249 ?

@qstokkink
Copy link
Contributor

Also, I notice some "CPU storms", but overall the GigaChannelCommunity seems pretty healthy:

afbeelding

@ichorid
Copy link
Contributor Author

ichorid commented Jun 27, 2019

#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...

@qstokkink
Copy link
Contributor

charting a safe path through a minefield...

I agree, maybe we should leave this for 7.4 then and focus on other stuff right now.

@ichorid
Copy link
Contributor Author

ichorid commented Jun 27, 2019

For 7.3 I'm going to address the most offending problems that are relatively simple to fix.

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

Successfully merging a pull request may close this issue.

2 participants