Each database worker thread accepts synchronization requests one at a time, but also concurrently with all other database
worker threads.
Each database worker thread uses one connection to the consolidated database. The MobiLink server opens one additional connection
for administrative purposes. So, the minimum number of connections from the MobiLink server to the consolidated database is
count + 1.
The number of database worker threads has a strong influence on MobiLink synchronization throughput, and you need to run tests
to determine the optimum number for your particular synchronization setup. The number of database worker threads determines
how many synchronizations can be active in the consolidated database simultaneously; the rest gets queued waiting for database
worker threads to become available. Adding database worker threads may increase throughput, but it also increases the possibility of contention between the active synchronizations. At some point
adding more database worker threads decreases throughput because the increased contention outweighs the benefit of overlapping
synchronizations.
The value set for this option is also the default setting for the -wu option, which can be used to limit the number of threads
that can simultaneously upload to the consolidated database. This is useful if the optimum number of database worker threads
for downloading is larger than the optimum number for uploading. The best throughput may be achieved with a large number of
database worker threads (via -w) with a small number allowed to apply uploads simultaneously (via -wu). In general, the optimum
number for -wu depends on the consolidated database, and is relatively independent of the processing or network speeds for
the remote databases. Therefore, when you increase the number of threads with -w, you may want to use -wu to restrict the
number that can upload simultaneously. For more information, see -wu mlsrv12 option.
The default number of database worker threads is 5.
Syntax