From b149d6d615a81b9d2830cd383f65e7a689447f58 Mon Sep 17 00:00:00 2001 From: David Kydd Date: Wed, 7 Nov 2018 13:54:17 +1300 Subject: [PATCH] Added note about provisioning times of containers vs. standard images --- docs/submitting_jobs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/submitting_jobs.md b/docs/submitting_jobs.md index d8f5900..aacf249 100644 --- a/docs/submitting_jobs.md +++ b/docs/submitting_jobs.md @@ -59,6 +59,7 @@ If there are referenced files that you wish to exclude from uploading, simply un The `Env` tab will allow you to configure the VMs to be deployed when you create a pool. You can select the VM type and either the Batch provided image (Windows / CentOS) or the container image to be run (currently CentOS only). The container image options displayed will change depending on which renderer is active for the current scene. +Container Images offer a wider variety of OS and Application versions, but currently take longer to provision to a new node in a pool (~7-12 minutes vs. ~3-5 minutes for Batch Provided Images). If you change scenes with the plugin window open, you will need to click 'Refresh' to trigger this list to update. You can see a list of VM types and their descriptions in [this article](https://azure.microsoft.com/pricing/details/virtual-machines/series/). Only VM's which include 8GB of Memory or greater are available for selection through the plugin, to match the minimum requirements of Maya 2017 / 2018.'