{"action":"opened","issue":{"url":"https://api.github.com/repos/wg/wrk/issues/197","repository_url":"https://api.github.com/repos/wg/wrk","labels_url":"https://api.github.com/repos/wg/wrk/issues/197/labels{/name}","comments_url":"https://api.github.com/repos/wg/wrk/issues/197/comments","events_url":"https://api.github.com/repos/wg/wrk/issues/197/events","html_url":"https://github.com/wg/wrk/issues/197","id":139519247,"number":197,"title":"Add option to control connection persistence (Keep-Alive)","user":{"login":"amichair","id":1410200,"avatar_url":"https://avatars.githubusercontent.com/u/1410200?v=3","gravatar_id":"","url":"https://api.github.com/users/amichair","html_url":"https://github.com/amichair","followers_url":"https://api.github.com/users/amichair/followers","following_url":"https://api.github.com/users/amichair/following{/other_user}","gists_url":"https://api.github.com/users/amichair/gists{/gist_id}","starred_url":"https://api.github.com/users/amichair/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amichair/subscriptions","organizations_url":"https://api.github.com/users/amichair/orgs","repos_url":"https://api.github.com/users/amichair/repos","events_url":"https://api.github.com/users/amichair/events{/privacy}","received_events_url":"https://api.github.com/users/amichair/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-09T09:14:26Z","updated_at":"2016-03-09T09:14:26Z","closed_at":null,"body":"Thanks for the great tool!\r\n\r\nIt would be very useful to add an option (-k?) to control whether Keep-Alive is enabled or not, so that one can test the load in different scenarios of web server and network configurations.\r\n\r\nEven better would be to specify then number of Keep-Alive requests per connection. For example, to better mimic the real load on a website, you could set this number to e.g. 10, such that on each client connection 10 requests are made and then the connection is closed, and the next request requires a new connection to be established. In this case a setting of 1 would be equivalent to no persistence (1 request per connection) and a setting of 0 might indicate unlimited persistence (which is the current and default behavior, if I understand the thin documentation correctly).\r\n"}}