{"__v":0,"_id":"586d3d84cd6e243900cfdd5f","category":{"project":"55faf11ba62ba1170021a9a7","version":"55faf11ba62ba1170021a9aa","_id":"586d3c287c6b5b2300c05055","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-01-04T18:17:12.683Z","from_sync":false,"order":18,"slug":"task-execution","title":"Task Execution"},"parentDoc":null,"project":"55faf11ba62ba1170021a9a7","user":"575e85ac41c8ba0e00259a44","version":{"__v":35,"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-01-04T18:23:00.422Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"Tools, like any other software, have their own CPU and memory requirements. Having a tool execute on an instance that does not provide adequate resources may cause that tool to run much slower than usual or to fail.\n\nOther tools require few resources and use only a very small fraction of an instance’s available computational resources. In this case, it makes sense to run several jobs on a single instance at the same time. Doing so not only lets the workflow complete faster, but may also quite significantly lower its cost.\n\nBecause tool resource requirements are crucial for [scheduling](doc:about-task-execution#section-scheduling) tool executions, every tool is expected to specify the resources it requires when a job is run. These parameters are already specified for tools available in Public Apps, and it is up to you to specify them for tools you upload to the Platform. If you do not specify resource requirements for the tools you upload to the Platform, default tool resource requirements will be used.\n\n##Specify resource requirements for your tools\nIf you are a tool developer, you can specify your tool's resource requirements [in the visual interface](doc:set-execution-hints-at-tool-level#section-via-the-visual-interface).\n\nYou can also specify these requirements via the API. For more information on setting these and other hints in general, read more about [setting hints at tool level using the API](doc:set-execution-hints-at-tool-level#section-via-the-api).\n\n###Default tool resource requirements\nIf a tool for any reason does not have its resource requirements specified, the Platform will assign it the default of 1 CPU core and 1024 MB of RAM.","excerpt":"","slug":"about-tool-resource-requirements","type":"basic","title":"About tool resource requirements"}

About tool resource requirements


Tools, like any other software, have their own CPU and memory requirements. Having a tool execute on an instance that does not provide adequate resources may cause that tool to run much slower than usual or to fail. Other tools require few resources and use only a very small fraction of an instance’s available computational resources. In this case, it makes sense to run several jobs on a single instance at the same time. Doing so not only lets the workflow complete faster, but may also quite significantly lower its cost. Because tool resource requirements are crucial for [scheduling](doc:about-task-execution#section-scheduling) tool executions, every tool is expected to specify the resources it requires when a job is run. These parameters are already specified for tools available in Public Apps, and it is up to you to specify them for tools you upload to the Platform. If you do not specify resource requirements for the tools you upload to the Platform, default tool resource requirements will be used. ##Specify resource requirements for your tools If you are a tool developer, you can specify your tool's resource requirements [in the visual interface](doc:set-execution-hints-at-tool-level#section-via-the-visual-interface). You can also specify these requirements via the API. For more information on setting these and other hints in general, read more about [setting hints at tool level using the API](doc:set-execution-hints-at-tool-level#section-via-the-api). ###Default tool resource requirements If a tool for any reason does not have its resource requirements specified, the Platform will assign it the default of 1 CPU core and 1024 MB of RAM.