{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenHFT/Chronicle-Core/issues/11","repository_url":"https://api.github.com/repos/OpenHFT/Chronicle-Core","labels_url":"https://api.github.com/repos/OpenHFT/Chronicle-Core/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/OpenHFT/Chronicle-Core/issues/11/comments","events_url":"https://api.github.com/repos/OpenHFT/Chronicle-Core/issues/11/events","html_url":"https://github.com/OpenHFT/Chronicle-Core/issues/11","id":153275674,"number":11,"title":"JLBH - Latency vs Load","user":{"login":"toaler","id":1082867,"avatar_url":"https://avatars.githubusercontent.com/u/1082867?v=3","gravatar_id":"","url":"https://api.github.com/users/toaler","html_url":"https://github.com/toaler","followers_url":"https://api.github.com/users/toaler/followers","following_url":"https://api.github.com/users/toaler/following{/other_user}","gists_url":"https://api.github.com/users/toaler/gists{/gist_id}","starred_url":"https://api.github.com/users/toaler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toaler/subscriptions","organizations_url":"https://api.github.com/users/toaler/orgs","repos_url":"https://api.github.com/users/toaler/repos","events_url":"https://api.github.com/users/toaler/events{/privacy}","received_events_url":"https://api.github.com/users/toaler/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-05T17:01:16Z","updated_at":"2016-05-05T17:01:16Z","closed_at":null,"body":"We were interested in using JLBH for testing how a features latencies scale while under loads (ie. 1, 2, 4, 8, etc threads of execution).\r\n\r\nI don't see that JLBH current allows the number of threads to be ramped up.  It seems like the code could be modified to run the test task concurrently.\r\n\r\nI'm curious if JLBH by design didn't support higher loads for a reason?  What is your take on this?  If there isn't a fundamental issue with supporting higher loads, we may try and make the necessary change to support this feature.  Any guidance for us before trying this out?"}}