{"action":"closed","issue":{"url":"https://api.github.com/repos/Atmosphere/atmosphere/issues/2056","labels_url":"https://api.github.com/repos/Atmosphere/atmosphere/issues/2056/labels{/name}","comments_url":"https://api.github.com/repos/Atmosphere/atmosphere/issues/2056/comments","events_url":"https://api.github.com/repos/Atmosphere/atmosphere/issues/2056/events","html_url":"https://github.com/Atmosphere/atmosphere/issues/2056","id":107908576,"number":2056,"title":"WriteOperation instances climbing","user":{"login":"poi212003","id":1898309,"avatar_url":"https://avatars.githubusercontent.com/u/1898309?v=3","gravatar_id":"","url":"https://api.github.com/users/poi212003","html_url":"https://github.com/poi212003","followers_url":"https://api.github.com/users/poi212003/followers","following_url":"https://api.github.com/users/poi212003/following{/other_user}","gists_url":"https://api.github.com/users/poi212003/gists{/gist_id}","starred_url":"https://api.github.com/users/poi212003/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/poi212003/subscriptions","organizations_url":"https://api.github.com/users/poi212003/orgs","repos_url":"https://api.github.com/users/poi212003/repos","events_url":"https://api.github.com/users/poi212003/events{/privacy}","received_events_url":"https://api.github.com/users/poi212003/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Atmosphere/atmosphere/labels/not%20a%20bug","name":"not a bug","color":"ededed"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-23T12:24:33Z","updated_at":"2015-09-23T14:45:55Z","closed_at":"2015-09-23T14:45:55Z","body":"Hi,\r\nI did a heap dump and for some reason the instance count of WriteOperation is climbing, the strange thing is that every instance is already marked as executed and completed.\r\nIs it possible that due to high sent rate, the scheduler executes slower than the rate the tasks are being added?\r\n\r\nIs there a way around it? or should I just remove the writeTimeout (use the default -1)? \r\n\r\nI'm using atmoshphere 1.0.13 - I know it's an old version, but I've checked the logic of the write timeout in the latest commit and it's still the same :)\r\n\r\nSee images attached:\r\n![instancecount](https://cloud.githubusercontent.com/assets/1898309/10044796/3973bb8e-61ed-11e5-83cd-79f79a025ad8.png)\r\n![instancecount1](https://cloud.githubusercontent.com/assets/1898309/10044801/3edb68f6-61ed-11e5-8ccb-1d8bcd41c228.png)\r\n\r\nRunning on:\r\nWindows server r2 x64 2008 standard\r\nRam 32GB\r\nNetwork 1gbps\r\nxeon e3-1230 v3\r\nApache Tomcat/7.0.62\t\r\njava 1.7.0_79-b15\r\n\r\nThanks.\r\nPavel"}}