Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Number of Rows per Match Job Batch Cycle

Number of Rows per Match Job Batch Cycle

This setting specifies an upper limit on the number of records that
Informatica MDM Hub
will process for matching during match process execution (Match or Auto Match and Merge jobs). When the match process starts executing, it begins by flagging records to be included in the
match job batch
. From the pool of new/unconsolidated records that are ready for match (CONSOLIDATION_IND=4), the match process changes CONSOLIDATION_IND to 3. The number of records flagged is determined by the Number of Rows per Match Job Batch Cycle. The match process then matches those records in the match job batch against all of the records in the base object.
The number of records in the match job batch affects how long the match process takes to execute. The value to specify depends on the size of your data set, the complexity of your match rules, and the length of the time window you have available to run the match process. The default match batch size is low (10). You increase this based on the number of records in the base object, as well as the number of matches generated for those records based on its match rules.
  • The lower your match batch size, the more times you will need to run the match and consolidation processes.
  • The higher your match batch size, the more work each match and consolidation process does.
For each base object, there is a medium ground where you reach the optimal match batch size. You need to identify this optimal batch size as part of performance tuning in your environment. Start with a match batch size of 10% of the volume of records to be matched and merged, run the match job only, see how many matches are generated by your match rules, and then adjust upwards or downwards accordingly.


We’d like to hear from you!