Warning Setting the concurrency too high can cause problems if your server does not have enough resources to handle it. The higher you raise the concurrency the bigger the server you are going to need to handle it. Please read Possible negative impacts below.

OttoFMS staring in version 4.2 can process more than one file at time. This is called concurrency. The default value is 1, meaning that only one file will be processed at a time. Multi-file deployments will go faster if your server can handle it. Single file deployments will not go any faster if you increase the concurrency.

You can change this value in each sub deployment when you have the Advanced Options enabled.

Possible negative impacts

Higher CPU usage

OttoFMS normally will only use one CPU to migrate data and to copy and move files. When you increase the concurrency, OttoFMS will use one CPU for each level of concurrency you set. So if you set it to 3 you can expect your server to use 3 CPUs to process the files. All of those CPUs may go to 100 percent utilization.

Higher memory usage

Each of those processes will also use it's own pile of memory. On a small 4GB server you will certainly run out of processing power and memory if you raise the concurrency higher than 1.

Linux without a swap file are more prone to problems

Linux servers that do not have a swap file will start killing other processes like FileMaker Server and Otto. If you are running a server without a swap file, please be very cautious when increasing the concurrency.