Closed adamrtalbot closed 5 months ago
Name | Link |
---|---|
Latest commit | 726d5a11242024a835deacc9ee1f1edd196d57ab |
Latest deploy log | https://app.netlify.com/sites/nextflow-docs-staging/deploys/66263d4f321f3a00087fa4a7 |
Deploy Preview | https://deploy-preview-4941--nextflow-docs-staging.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
fixes #4304
@adamrtalbot how would these all play out in the nextflow code:
Standard_e*d_v5
Standard_e*_v5
Standard_e*_v*
Standard_e*
What is the priority of choosing a VM. Does it limit to the Family and then match the compute requirements?
@adamrtalbot how would these all play out in the nextflow code:
Standard_e*d_v5
Standard_e*_v5
Standard_e*_v*
Standard_e*
What is the priority of choosing a VM. Does it limit to the Family and then match the compute requirements?
You can see the code here: https://github.com/nextflow-io/nextflow/blob/54ad624162f78f66ea8562fc6941442404672648/plugins/nf-azure/src/main/nextflow/cloud/azure/batch/AzBatchService.groovy#L178-L234
Adds details about the Azure Batch autopool feature including how to use variable sized pools and nodes. Should make it more obvious to end users that Nextflow supports splitting work across variable sized machines.
Closes #4304 (kinda, it documents a feature that already existed).