This reference architecture document provides guidance for CloudSoda deployments. Included is the reference architecture for a CloudSoda controller and CloudSoda agents. For specific use cases please work with the CloudSoda team on specifics for your solution.
The tables below outline the recommended architecture for servers and VMs and include cloud templates that can be used.
Things to know:
- The CloudSoda controller requires a minimum 500GB of storage on the primary partition.
- 100 million files or scanning hourly should consider more storage on their controller node, please contact the CloudSoda team for details.
The tables below outline the recommended architecture for servers and VMs,
and include cloud templates that can be used. These values should only serve as a guideline. The proper specification should be adjusted based on the dataset, storage type, and network speed involved in the data transfer.
Things to know:
- An agent can run on almost any architecture to enable data movement including laptops, servers, VMs, and other platforms.
- The performance of the data movement is dependent on the number of cores and memory available to the agent. The more cores & memory you have available the faster the agent will perform.
- We recommend a three-to-one memory-to-core ratio for cloud transfers.
- For agents doing data movement to and from the cloud or an object store, using a processor that has integrated SHA extension will give approximately a 30% increase in performance. For a list of processors, click on the links below: