com.informatica.mdm.batchcontroller.BatchJob.min_rec_for_multithreading

This property is available in the

cmxcleanse.properties

file.

When the number of records reaches the specified value, multithreading starts on all the batch jobs. To disable multithreading, you must set the property value to 1.

Total number of threads used by the Master or Slave Process Server when executing. Generate Match Tokens after Load, Match, and Stage jobs.

Maximum number of threads to use for a batch process.

For example, if the host machine has 16 CPU cores, set the Threads for Batch Processing in the Process Server registration to 64. Based on the usage and requirements, you can set a higher value. Applicable only if the Process Server is marked for batch processing.

com.informatica.mdm.loadbalance.ControllerThread.timeout

This property is found in the

cmxcleanse.properties

file.

When distributing the load to different slave Process Servers, after the last block is sent to a slave Process Server, all slave Process Servers which are processing the blocks MUST complete the job within the timeout period.

cmx.server.batch.load.analyze_threshold_rate

Available in

cmxserver.properties

For ORACLE only. Available from MDM 10.0 HotFix 1.

Specifies the frequency that the MDM Hub gathers analytical statistics for tables affected by a batch Load job. Set to 0 to disable statistic collection. Set to 1 to collect statistics only at the end of a Load job for base object and cross-reference tables.

For example, if the threshold is 10, then statistics would be gathered at every 10^n records. For example, new statistics would be gathered whenever the insert record count reaches 100, 1000, 10000, and so on.

com. informatica.mdm.batchserver.RecyclerThread.max_idling

This property is found in the

cmxcleanse.properties

file.

If a slave Process Server is processing a block of batch job and is idle for a duration specified in this attribute then the specific thread is marked as 'dead.'

cmx.server.automerge.threads_per_job

This property is found in the

cmxserver.properties

file.

Maximum number of threads distributed across different Process Servers to process the automerge job.

For example, if this value is 20, automerge would be distributed across two Process Servers each with 10. The distribution depends on factors such as CPU weightage of the Process Server and other jobs running on the Process Server.

This value must be less than the value in 'Threads for Batch' attribute specified for the Process Server.

cmx.server.automerge.block_size

This property is found in the

cmxserver.properties

file.

Maximum number of records to be sent for merges to each Process Server in one block.

For example, consider the scenario of two Process Servers with 1000 records to be merged. If this value is 250, each Process Server gets 250 records first followed by another 250 records next.

Increasing this value can provide performance improvement based on how powerful the application servers and database servers are.

cmx.server.batch.threads_per_job

This property is found in the

cmxserver.properties

file.

Maximum number of threads distributed across different Process Servers to process the load job.

For example, if this value is 20 then load process would be distributed across two Process Servers each with 10. The distribution depends on factors such as CPU weightage of the Process Server and other jobs running on the Process Server.

This value must be less than the value in 'Threads for Batch' attribute specified for the Process Server.

cmx.server.batch.load.block_size

This property is found in the

cmxserver.properties

file.

Maximum number of records in one block for each Process Server.

For example, consider the scenario of two Process Servers with 1000 records to load. If the specified value is 250, each Process Server gets 250 records first followed by another 250 records next.

Increasing this value can provide performance improvement based on how powerful the application servers and database servers are.

See 'Threads for Cleanse Processing' attribute described earlier.

Note that, this thread attribute is different from the core threads per job attribute of the load job described earlier.

If 'Generate Match Tokens on Load' is not selected, this attribute does not have any impact on the performance of the Load job.

cmx.server.validate.lookup.timeline.onload

This property is found in the

cmxserver.properties

file.

For timeline enabled BO, the XREF is validated for the correct timeline among multiple timeline values, before selecting a valid lookup row. If the load job is taking more time and heap memory, when you have the timeline enabled BO and inserts large lookup stream cluster, then you must enable this property in the

cmxserver.properties

s file.

cmx.server.batch.threads_per_job

This property is found in the

cmxserver.properties

file.

Same property, re-used from LOAD Job. See LOAD Job section for more details.

cmx.server.batch.recalculate.block_size

This property is found in the

cmxserver.properties

file.

Maximum number of records to be sent, to recalculate BVT, to each Process Server in one block.

For example, consider the scenario of two Process Servers with 1000 records to be recalculated. If this value is 250, each Process Server gets 250 records first followed by another 250 records next.

Increasing this value can provide performance improvement based on how powerful the application servers and database servers are.

cmx.server.batch.threads_per_job

Available in

cmxserver.properties

Same property, re-used from LOAD Job. Refer to LOAD Job section for more details.

cmx.server.batch.batchunmerge.block_size

This property is found in the

cmxserver.properties

file.

Maximum number of records to be sent for unmerges, to each Process Server in one block.

For example, consider the scenario of two Process Servers with 1000 records to be unmerged. If this value is 250, each Process Server gets 250 records first followed by another 250 records next.

Increasing this value can provide performance improvement based on how powerful the application servers and database servers are.

cmx.server.batch.threads_per_job

This property is found in the

cmxserver.properties

file.

Same property, re-used from LOAD Job. See LOAD Job section for more details.

cmx.server.batch.delete.block_size

This property is found in the

cmxserver.properties

file.

Maximum number of records to be sent for deletion, to each Process Server in one block.

For example, consider the scenario of two Process Servers with 1000 records to be deleted. If this value is 250, each Process Server first gets 250 records and then another 250 records.

Increasing this value can provide performance improvement. This performance improvement depends on how powerful the application servers and database servers are.

cmx.server.tokenize.file_load

This property is found in the

cmxcleanse.properties

file.

Applicable for Oracle and Db2. The MS SQL Server always uses Java.

If true, Db2 file loader or Oracle SQL Loader is used to load the records during the tokenization job.

If file writing is causing performance issue, this can be changed to false, thereby, data is directly written to the database every time instead of file loader option. Generally, file loader is faster than the direct database writes. You might choose the option according to your environment.

cmx.server.cleanse.min_size_for_distribution

This property is found in the

cmxcleanse.properties

file.

The MDM Hub distributes the cleanse job across different cleanse server only if the number of records is higher than this minimum size.

When distributing the load, each slave Process Server would use the Cleanse Thread Count for the number of worker threads.

cmx.server.java_jdbc_loader

Applicable for Oracle and Db2.

Default is false.

This property is found in the

cmxcleanse.properties

file.

If true, Db2 and Oracle use direct database connections during the stage job instead of Db2 file loader or Oracle SQL loader options

If file writing is causing performance issue, this can be changed to true. On doing so, data gets directly written to the database every time instead of file loader option. Note that, generally, file loader is faster than the direct database write. You might choose the option according to your environment.

cmx.server.match.distributed_match

This property is found in the

cmxcleanse.properties

file.

The MDM Hub distributes the match job across different cleanse server only if this value is set to 1.

When distributing the load, each slave Process Server would use the Cleanse Thread Count for the number of worker threads.

cmx.server.match.file_load

Applicable for Oracle and Db2.

This property is found in the

cmxcleanse.properties

file.

If true, Db2 file loader or Oracle SQL Loader is used to load the records during the tokenization job. Microsoft SQL Server always uses the Java Database Connectivity (JDBC) loader.

If file writing causes performance issue, change it to false to directly write data to the database every time instead of file loader option. Generally, file loader is faster than the direct database writes. You might choose the option according to your environment.

cmx.server.match.loader_batch_size

This property is found in the

cmxcleanse.properties

file.

Applicable if JDBC load is used in match processing instead of file loader option.

Maximum number of records to be sent for match in each worker thread.

Increasing this value can provide performance improvement based on how powerful the application servers and database servers are.

The execution timeout in minutes when executing a match rule. If this time is reached, the match process will exit. This must be increased only if the match rule and the data are very complex. Generally rules must be able to complete within 20 minutes.

Maximum number of records to be processed by the MDM Hub for matching. This number would affect the duration of match process.

Also, lower the match batch size, you have to run the match process more times.

This property is found in the

cmxcleanse.properties

file.

Number of records per match ranger node (limits memory use). Ranger is an internal component used within the match process where sorting and merging operations are performed based on this maximum records attribute.

You can optimize this value to get better performance based on the memory available in your application server.

cmx.server.batch.smartsearch.initial.block_size

This property is available in the

cmxserver.properties

file.

Maximum number of records that the initially index smart search data batch job can process in each block. This property is not applicable through regular indexing outside this specific batch job. Based on the power of your application server, you can increase this value to improve the performance.

cmx.server.batch.threads_per_job

This property is available in the

cmxserver.properties

file.

Maximum number of threads distributed across different Process Servers to process the batch job initially index smart search data. You can increase this value to achieve more performance during this batch job. This property is not applicable for regular indexing outside this specific batch job.

cmx.ss.index.build.optimization=true

This property is available in the

cmxserver.properties

and

cmxcleanse.properties

files. If the smart search indexing from a load job takes more time in a specific model, set this property for a better optimization on the indexing.