{"action":"created","issue":{"url":"https://api.github.com/repos/gocd/gocd/issues/496","labels_url":"https://api.github.com/repos/gocd/gocd/issues/496/labels{/name}","comments_url":"https://api.github.com/repos/gocd/gocd/issues/496/comments","events_url":"https://api.github.com/repos/gocd/gocd/issues/496/events","html_url":"https://github.com/gocd/gocd/issues/496","id":42619501,"number":496,"title":"Probable memory leak in go server","user":{"login":"NachbarsLumpi","id":8520682,"avatar_url":"https://avatars.githubusercontent.com/u/8520682?v=3","gravatar_id":"","url":"https://api.github.com/users/NachbarsLumpi","html_url":"https://github.com/NachbarsLumpi","followers_url":"https://api.github.com/users/NachbarsLumpi/followers","following_url":"https://api.github.com/users/NachbarsLumpi/following{/other_user}","gists_url":"https://api.github.com/users/NachbarsLumpi/gists{/gist_id}","starred_url":"https://api.github.com/users/NachbarsLumpi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NachbarsLumpi/subscriptions","organizations_url":"https://api.github.com/users/NachbarsLumpi/orgs","repos_url":"https://api.github.com/users/NachbarsLumpi/repos","events_url":"https://api.github.com/users/NachbarsLumpi/events{/privacy}","received_events_url":"https://api.github.com/users/NachbarsLumpi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2014-09-12T11:23:16Z","updated_at":"2015-02-11T13:13:22Z","closed_at":null,"body":"After about two weeks the go server java process consumes more than 1.5GB memory. Even though we have more than 50 pipelines this is quite a lot!"},"comment":{"url":"https://api.github.com/repos/gocd/gocd/issues/comments/73878583","html_url":"https://github.com/gocd/gocd/issues/496#issuecomment-73878583","issue_url":"https://api.github.com/repos/gocd/gocd/issues/496","id":73878583,"user":{"login":"arvindsv","id":172235,"avatar_url":"https://avatars.githubusercontent.com/u/172235?v=3","gravatar_id":"","url":"https://api.github.com/users/arvindsv","html_url":"https://github.com/arvindsv","followers_url":"https://api.github.com/users/arvindsv/followers","following_url":"https://api.github.com/users/arvindsv/following{/other_user}","gists_url":"https://api.github.com/users/arvindsv/gists{/gist_id}","starred_url":"https://api.github.com/users/arvindsv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arvindsv/subscriptions","organizations_url":"https://api.github.com/users/arvindsv/orgs","repos_url":"https://api.github.com/users/arvindsv/repos","events_url":"https://api.github.com/users/arvindsv/events{/privacy}","received_events_url":"https://api.github.com/users/arvindsv/received_events","type":"User","site_admin":false},"created_at":"2015-02-11T13:13:22Z","updated_at":"2015-02-11T13:13:22Z","body":"Can you add monitoring of the number of items in cache, to that script? It should be a line in the output which looks like this:\r\n\r\n```\r\nCache size: 14928 (Accuracy: Best Effort)\r\n```\r\n\r\nI want to know if the number of items is increasing. It'll be a little hard to know what's in it, since this is just a count, not size of the cache. But, it would be useful to know how it correlates to the heap and slowdown. I see from an earlier output that you've set it to use 1024m of Xmx. If my suspicion about the cache is right, then setting that higher should mean the cache can grow higher, and it'll stop being unresponsive.\r\n\r\nAnother option, as I mentioned, would be to add an option to control the cache size. I can add it into code, if we think there's a correlation between heap size and cache size."}}