{"action":"created","issue":{"url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/141","repository_url":"https://api.github.com/repos/malawski/cloudworkflowsimulator","labels_url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/141/labels{/name}","comments_url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/141/comments","events_url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/141/events","html_url":"https://github.com/malawski/cloudworkflowsimulator/issues/141","id":153585686,"number":141,"title":"Should we consider cache/RAM usage while assigning tasks to VMs?","user":{"login":"aciepiela","id":8086628,"avatar_url":"https://avatars.githubusercontent.com/u/8086628?v=3","gravatar_id":"","url":"https://api.github.com/users/aciepiela","html_url":"https://github.com/aciepiela","followers_url":"https://api.github.com/users/aciepiela/followers","following_url":"https://api.github.com/users/aciepiela/following{/other_user}","gists_url":"https://api.github.com/users/aciepiela/gists{/gist_id}","starred_url":"https://api.github.com/users/aciepiela/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aciepiela/subscriptions","organizations_url":"https://api.github.com/users/aciepiela/orgs","repos_url":"https://api.github.com/users/aciepiela/repos","events_url":"https://api.github.com/users/aciepiela/events{/privacy}","received_events_url":"https://api.github.com/users/aciepiela/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/labels/functionality","name":"functionality","color":"d7e102"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-05-07T09:50:10Z","updated_at":"2016-05-24T15:02:56Z","closed_at":"2016-05-24T15:02:56Z","body":"Right now when we have homogenous, one-core VMs we don't care whether a tasks input/output files can fit in a VMs memory, because if they don't then the whole cloud doesn't make any sense.\r\n\r\nBut when we consider heterogenous clouds with multi-core VMs I think we should include this. We assume that every task will run on each core so input/output files for all tasks may not fit in memory at once. \r\n\r\nI've checked what's the maximum sum of all input/output files for a single task and here are the results:\r\nCYBERSHAKE - 39GB\r\nGENOME - 14GB\r\nLIGO - 53MB\r\nMONTAGE - 1GB\r\n\r\nSo for Cybershake and Genome they are significant. With an 8-core VM we may theoretically need 8 * 39 GB Ram to run all tasks. Otherwise some tasks may have to wait in a queue or use disk instead of RAM.\r\n\r\nSo, should we include RAM (and its current usage) while assigning tasks to VMs?\r\nCalling @pkoniu , @malawski , @ziaber "},"comment":{"url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/comments/221300140","html_url":"https://github.com/malawski/cloudworkflowsimulator/issues/141#issuecomment-221300140","issue_url":"https://api.github.com/repos/malawski/cloudworkflowsimulator/issues/141","id":221300140,"user":{"login":"aciepiela","id":8086628,"avatar_url":"https://avatars.githubusercontent.com/u/8086628?v=3","gravatar_id":"","url":"https://api.github.com/users/aciepiela","html_url":"https://github.com/aciepiela","followers_url":"https://api.github.com/users/aciepiela/followers","following_url":"https://api.github.com/users/aciepiela/following{/other_user}","gists_url":"https://api.github.com/users/aciepiela/gists{/gist_id}","starred_url":"https://api.github.com/users/aciepiela/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aciepiela/subscriptions","organizations_url":"https://api.github.com/users/aciepiela/orgs","repos_url":"https://api.github.com/users/aciepiela/repos","events_url":"https://api.github.com/users/aciepiela/events{/privacy}","received_events_url":"https://api.github.com/users/aciepiela/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T15:02:56Z","updated_at":"2016-05-24T15:02:56Z","body":"So as per today meeting, we decided that we can store input/output files on a VM's hard drive and that we shouldn't consider RAM when assigning tasks to VMs. \r\n\r\nThis may be a future extension though. "}}
{"actor":{"display_login":"aciepiela"}}