{"action":"opened","issue":{"url":"https://api.github.com/repos/rabbitmq/rabbitmq-management/issues/164","repository_url":"https://api.github.com/repos/rabbitmq/rabbitmq-management","labels_url":"https://api.github.com/repos/rabbitmq/rabbitmq-management/issues/164/labels{/name}","comments_url":"https://api.github.com/repos/rabbitmq/rabbitmq-management/issues/164/comments","events_url":"https://api.github.com/repos/rabbitmq/rabbitmq-management/issues/164/events","html_url":"https://github.com/rabbitmq/rabbitmq-management/issues/164","id":144779587,"number":164,"title":"the management statistics database with large queue,  version 3.6.1","user":{"login":"zengzhenbo","id":5714670,"avatar_url":"https://avatars.githubusercontent.com/u/5714670?v=3","gravatar_id":"","url":"https://api.github.com/users/zengzhenbo","html_url":"https://github.com/zengzhenbo","followers_url":"https://api.github.com/users/zengzhenbo/followers","following_url":"https://api.github.com/users/zengzhenbo/following{/other_user}","gists_url":"https://api.github.com/users/zengzhenbo/gists{/gist_id}","starred_url":"https://api.github.com/users/zengzhenbo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zengzhenbo/subscriptions","organizations_url":"https://api.github.com/users/zengzhenbo/orgs","repos_url":"https://api.github.com/users/zengzhenbo/repos","events_url":"https://api.github.com/users/zengzhenbo/events{/privacy}","received_events_url":"https://api.github.com/users/zengzhenbo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-31T03:33:45Z","updated_at":"2016-03-31T03:33:45Z","closed_at":null,"body":"since we upgraded rabbitmq from 3.5.7 to 3.6.1, the managment ui notice that:\r\n\r\n> The management statistics database currently has a queue of X events to process. If this number keeps increasing, so will the memory used by the management plugin. \r\n\r\n\r\nand the memory  continuously increases.\r\nIn rabbitmq config file, `rates_mode` has been set like this:\r\n**{rabbitmq_management, [{rates_mode, none}]}\r\n**\r\nit seem that mgmt_db_handler set `collect_statistics` with value `coarse`(line 83 in `rabbit_mgmt_db_handler.erl`).\r\n\r\nIs there a way to solve this problem without disabled `rabbitmq_management`, and keep `rates_mode` with value `none`?"}}