{"action":"created","issue":{"url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/2","repository_url":"https://api.github.com/repos/wekan/wekan-mongodb","labels_url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/2/comments","events_url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/2/events","html_url":"https://github.com/wekan/wekan-mongodb/issues/2","id":222129043,"number":2,"title":"Excessive CPU usage","user":{"login":"johnniesong","id":4927765,"avatar_url":"https://avatars3.githubusercontent.com/u/4927765?v=4","gravatar_id":"","url":"https://api.github.com/users/johnniesong","html_url":"https://github.com/johnniesong","followers_url":"https://api.github.com/users/johnniesong/followers","following_url":"https://api.github.com/users/johnniesong/following{/other_user}","gists_url":"https://api.github.com/users/johnniesong/gists{/gist_id}","starred_url":"https://api.github.com/users/johnniesong/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/johnniesong/subscriptions","organizations_url":"https://api.github.com/users/johnniesong/orgs","repos_url":"https://api.github.com/users/johnniesong/repos","events_url":"https://api.github.com/users/johnniesong/events{/privacy}","received_events_url":"https://api.github.com/users/johnniesong/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2017-04-17T13:06:08Z","updated_at":"2017-11-23T21:44:32Z","closed_at":null,"author_association":"NONE","body":"https://github.com/wekan/wekan/issues/718 this issue also happened on your docker ENV.\r\n\r\nDowngrading from Node 6.10.0 to v4.8.1 solved the 100% CPU issue\r\n"},"comment":{"url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/comments/346701078","html_url":"https://github.com/wekan/wekan-mongodb/issues/2#issuecomment-346701078","issue_url":"https://api.github.com/repos/wekan/wekan-mongodb/issues/2","id":346701078,"user":{"login":"GavinLilly","id":29777802,"avatar_url":"https://avatars0.githubusercontent.com/u/29777802?v=4","gravatar_id":"","url":"https://api.github.com/users/GavinLilly","html_url":"https://github.com/GavinLilly","followers_url":"https://api.github.com/users/GavinLilly/followers","following_url":"https://api.github.com/users/GavinLilly/following{/other_user}","gists_url":"https://api.github.com/users/GavinLilly/gists{/gist_id}","starred_url":"https://api.github.com/users/GavinLilly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GavinLilly/subscriptions","organizations_url":"https://api.github.com/users/GavinLilly/orgs","repos_url":"https://api.github.com/users/GavinLilly/repos","events_url":"https://api.github.com/users/GavinLilly/events{/privacy}","received_events_url":"https://api.github.com/users/GavinLilly/received_events","type":"User","site_admin":false},"created_at":"2017-11-23T21:44:32Z","updated_at":"2017-11-23T21:44:32Z","author_association":"NONE","body":"I started setting up Kadira but didn't get round to profiling. Other things took priority. I will be able to look at it in mid-December. I agree with your hypothesis in that perhaps Meteor might be trying to do too much to update to each client.\r\nFor the time being I've doubled the number of running Wekan instances to 6 across 3 dual core VMs. It seems more stable but the instances are still reaching 100% load.\r\n\r\nOn the MongoDB side I've not observed any increased CPU or RAM load so some form of search could be possible. I'd be a little concerned about it searching using a cursor instead of an index though"}}
{"actor":{"display_login":"GavinLilly"}}