Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Latest commit

 

History

History
24 lines (13 loc) · 1.38 KB

30-storage-overview.md

File metadata and controls

24 lines (13 loc) · 1.38 KB

Storage Options

Each environment creates an Azure Files share, but this isn't always sufficient if you have hundreds or thousands of virtual machines in your render farm due to the IOPS and throughput required to support these higher numbers of virtual machines.

Render Hub supports two storage options that target different sized render farms, a File Server (NFS) or Avere vFXT cluster.

File Server (NFS)

The File Server option deploys a dedicated Linux (CentOS 7.6) virtual machine with a single NFS export. The virtual machine has 8 disks, configured and formatted in a RAID 0 setup to offer maximum IOPS.

This option is recommended for render farms with tens or low hundreds of virtual machines. Since the deployment is a single File Server it is not highly-available.

For details on deploying a File Server see here.

Avere vFXT cluster

For render farms with hundreds or thousands of virtual machines, Avere vFXT is the recommended option. An Avere vFXT cluster caches input data in memory and is resilient to node failure. The cluster can scale from 3 to 12 virtual machines, increasing IOPS and throughput.

For more information on Avere vFXT see here.

For details on deploying an Avere vFXT cluster see here.

Return to the Render Hub docs.