{"action":"created","issue":{"url":"https://api.github.com/repos/executors/issaquah_2016/issues/21","repository_url":"https://api.github.com/repos/executors/issaquah_2016","labels_url":"https://api.github.com/repos/executors/issaquah_2016/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/executors/issaquah_2016/issues/21/comments","events_url":"https://api.github.com/repos/executors/issaquah_2016/issues/21/events","html_url":"https://github.com/executors/issaquah_2016/issues/21","id":175800976,"number":21,"title":"Should we add an execution resource that supports bulk execute and the networking TS","user":{"login":"fraggamuffin","id":6393929,"avatar_url":"https://avatars.githubusercontent.com/u/6393929?v=3","gravatar_id":"","url":"https://api.github.com/users/fraggamuffin","html_url":"https://github.com/fraggamuffin","followers_url":"https://api.github.com/users/fraggamuffin/followers","following_url":"https://api.github.com/users/fraggamuffin/following{/other_user}","gists_url":"https://api.github.com/users/fraggamuffin/gists{/gist_id}","starred_url":"https://api.github.com/users/fraggamuffin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fraggamuffin/subscriptions","organizations_url":"https://api.github.com/users/fraggamuffin/orgs","repos_url":"https://api.github.com/users/fraggamuffin/repos","events_url":"https://api.github.com/users/fraggamuffin/events{/privacy}","received_events_url":"https://api.github.com/users/fraggamuffin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-08T16:33:19Z","updated_at":"2016-09-09T21:57:25Z","closed_at":null,"body":"We (Gordon and I ) realize this is suppose to be minimal, and that we added thread pool resource support because everyone wants it, but we wonder if we can also add an execution resource that supports bulk execute.\r\nRationale: the execute functions for these are being included in the minimal paper so  it make sense to also include the execution resource that is associated with them. This doesn't have to be particularly complex definition, but we believe we should provide something like this as base for future work.\r\n\r\nMore detail available on request.\r\n\r\nWe can also add a separate resource for the Networking TS."},"comment":{"url":"https://api.github.com/repos/executors/issaquah_2016/issues/comments/246051998","html_url":"https://github.com/executors/issaquah_2016/issues/21#issuecomment-246051998","issue_url":"https://api.github.com/repos/executors/issaquah_2016/issues/21","id":246051998,"user":{"login":"AerialMantis","id":12399605,"avatar_url":"https://avatars.githubusercontent.com/u/12399605?v=3","gravatar_id":"","url":"https://api.github.com/users/AerialMantis","html_url":"https://github.com/AerialMantis","followers_url":"https://api.github.com/users/AerialMantis/followers","following_url":"https://api.github.com/users/AerialMantis/following{/other_user}","gists_url":"https://api.github.com/users/AerialMantis/gists{/gist_id}","starred_url":"https://api.github.com/users/AerialMantis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AerialMantis/subscriptions","organizations_url":"https://api.github.com/users/AerialMantis/orgs","repos_url":"https://api.github.com/users/AerialMantis/repos","events_url":"https://api.github.com/users/AerialMantis/events{/privacy}","received_events_url":"https://api.github.com/users/AerialMantis/received_events","type":"User","site_admin":false},"created_at":"2016-09-09T21:57:25Z","updated_at":"2016-09-09T21:57:25Z","body":"The execution resource I had in mind was something that would be designed to support the bulk_*_execute() functions, the primary difference would be that the sub executor class defined within the resource would have bulk_execute(), bulk_async_execute() and bulk_then_execute(). Another difference would be that instead of the attach() member function you would have a wait() member function that would essentially wait for all asynchronous execution agents to finish, though observably this behaviour would be similar to that of attach().\r\n\r\nHowever if the intention is that the thread_pool support the bulk_*_execute() functions as well then I believe that the thread_pool would solve this purpose providing the basic_executor can be specialised, removing the need for an additional resource, which I believe would be preferable for the minimal paper.\r\n\r\nThough I would suggest that we consider altering the name of the resource to agent_pool instead to align with the convention of executors executing light weight execution agents?"}}
{"actor":{"display_login":"AerialMantis"}}