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

High CPU usage for channels with lots of members #61

Closed
GoogleCodeExporter opened this Issue Jun 13, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Jun 13, 2015

Channel lwt has hundreds of members, and this leads to high CPU usage for all 
requests/XMPP 
messages that it receives. I'm suspecting that this is caused by 
attachUsersToChannelMembers/getUsersByChannel. Sample Appstats output for one 
of their 
messages:

http://partychapp.appspot.com/appstats/details?time=1273421263242

In case it's gone, screenshot at:

http://skitch.com/mihaiparparita/dnir5/appstats-partychapp

All of the datastore_v3.Next calls is paging through the query that 
getUsersByChannel does.

Ideally we shouldn't load the User for every Member at all, we don't care about 
it (except for the 
requesting user's User).

Original issue reported on code.google.com by mihai.parparita on 9 May 2010 at 4:10

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Jun 13, 2015

Getting there with the changes to only load the User for the requesting user.

Original comment by mihai.parparita on 10 May 2010 at 3:51

  • Changed state: Accepted
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Jun 13, 2015

This issue was closed by revision r195.

Original comment by mihai.parparita on 10 May 2010 at 1:30

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment