{"action":"opened","issue":{"url":"https://api.github.com/repos/hyrise/hyrise/issues/1005","repository_url":"https://api.github.com/repos/hyrise/hyrise","labels_url":"https://api.github.com/repos/hyrise/hyrise/issues/1005/labels{/name}","comments_url":"https://api.github.com/repos/hyrise/hyrise/issues/1005/comments","events_url":"https://api.github.com/repos/hyrise/hyrise/issues/1005/events","html_url":"https://github.com/hyrise/hyrise/issues/1005","id":345650972,"node_id":"MDU6SXNzdWUzNDU2NTA5NzI=","number":1005,"title":"Multithreaded Benchmarks","user":{"login":"mrks","id":575106,"node_id":"MDQ6VXNlcjU3NTEwNg==","avatar_url":"https://avatars2.githubusercontent.com/u/575106?v=4","gravatar_id":"","url":"https://api.github.com/users/mrks","html_url":"https://github.com/mrks","followers_url":"https://api.github.com/users/mrks/followers","following_url":"https://api.github.com/users/mrks/following{/other_user}","gists_url":"https://api.github.com/users/mrks/gists{/gist_id}","starred_url":"https://api.github.com/users/mrks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrks/subscriptions","organizations_url":"https://api.github.com/users/mrks/orgs","repos_url":"https://api.github.com/users/mrks/repos","events_url":"https://api.github.com/users/mrks/events{/privacy}","received_events_url":"https://api.github.com/users/mrks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-30T08:00:02Z","updated_at":"2018-07-30T08:00:02Z","closed_at":null,"author_association":"MEMBER","body":"The benchmark runner is a good tool to evaluate our performance. Currently, it only executes one query at a time (which might be executed with multiple threads). @lanice built some [cool graphs](https://github.com/hyrise/hyrise/pull/994#issuecomment-408680431) for multi-threaded multi-client benchmarks.\r\n\r\nIt should be possible to run this as easily as the current benchmarks are and get a similar graph. Because this only makes sense with a plot, I think we should not embed this in the runner, but have a wrapper script for the runner.\r\n\r\nInteresting command line options:\r\n- number of clients (i.e., queries running in parallel)\r\n- number of queries / max execution time\r\n- thread stepping (for a quick evaluation, it should be enough to evaluate 1, 2, 3, 4, 5, 10, 15, ... threads)\r\n\r\nBefore we start to work on this, let's discuss it."}}
{"actor":{"display_login":"mrks"}}