Recommendations for Performance Tuning

Performance tuning options are set on the Performance Tuning tab of the execution options.

The optimum performance settings for a particular project depend on many things. The number of form mappings, the level of interdependency between mappings, the number of records being migrated, the ability of each server to support multiple connections, and the number of cores available to the machine running Precision Bridge. Below follows some general advice for selecting the optimum settings:

• Do not configure too many connections. Seek advice from the server administrator if you are unsure how many connections might be supported concurrently. If the number is too high, you risk timeouts and a visible slowdown for other users of the server. In most cases, however, 10 concurrent connections or less will not cause issues, and you may be able to go much higher for powerful production servers.
• As a rule of thumb, keep approximately the following ratio: max number of source connections x 2 = number of retrieve threads X number of parallel form mappings. For example, 10 source connections x2 = 4 retrieve threads X 5 parallel form mappings. 
• As a rule of thumb, keep approximately the following ratio: max number of target connections x 2 = number of submit threads X number of parallel form mappings. For example, 10 target connections x2 = 4 submit threads X 5 parallel form mappings. 
• If source deletions are configured (archive projects) add additional source connections to cover multi threading for this process if the number of source deletion threads being used is greater than the number of retrieval threads. For example, 20 source connections x2 = MAX[4 retrieve threads & 8 source delete threads] X 5 parallel form mappings. 
• For projects where there are a large number of form mappings (>20) but each form mapping will likely migrate a relatively small number of records (<1000), performance is likely to be improved more by increasing the number of parallel form mappings and keeping the number of retrieve/submit threads relatively small. For example, for 10 connections on source and target, you might specify 2 threads for retrieve, 2 for submit and 10 parallel form mappings.
• For projects where there are a relatively small number of form mappings (<20) but a large number of records per form mapping (>10000), performance is likely to be improved more by increasing the number of retrieve and submit threads and keeping the number of parallel form mappings. For example, for 10 connections on source and target, you might specify 10 threads for retrieve, 10 for submit and 2 parallel form mappings.
• Do remember that you can also set the number of threads for retrieve and submit individually for each form mapping if required in the Options->Advanced tab of the form mapping. (see below)

• If your project is reporting timeouts when executing, reduce the number of connections and number of threads/parallel form mappings before re-trying. You can also try reducing the batch sizes for retrieval, submit and source deletion.

Related Articles

Performance Tuning in Precision Bridge

Defining Advanced Execution Options

Form Mapping Options