Table of Contents

Search

  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

Optimizing the Tokenize and Merge Process Performance

Optimizing the Tokenize and Merge Process Performance

To optimize the performance of the tokenize and merge process for the MDM Hub environment, add the optimization properties to the
cmxcleanse.properties
file.
  1. Open the
    cmxcleanse.properties
    file in the following directory:
    On UNIX.
    <infamdm installation directory>/hub/cleanse/resources
    On Windows.
    <infamdm installation directory>\hub\cleanse\resources
  2. To optimize the performance of the tokenize and merge process, add the optimization properties to the
    cmxcleanse.properties
    file.
    The following table describes the optimization properties that you can configure:
    Property
    Description
    cmx.server.stripDML.useUpdate
    IBM DB2 only. When set to
    true
    , configures the MDM Hub to update the status of the match tokens that are not required as not valid instead of deleting them from the match key table.Default is
    false
    .
    The update to the status of the match tokens that are not valid is more efficient than the delete operation that removes the match tokens that are not valid.
    When you set the property to
    true
    , to remove records that are not valid, ensure that you periodically clean up the match key tables.
    cmx.server.stripDML.blockSize
    Number of records that the MDM Hub processes in each block. Default is
    100
    .
    cmx.server.stripDML.noOfThreadsForInsert
    Number of threads that the MDM Hub uses to insert records into the match key tables. Default is
    50
    .
    cmx.server.stripDML.noOfThreadsForUpdate
    Number of threads that the MDM Hub uses to update records in the match key tables. Default is
    30
    .
    cmx.server.stripDML.noOfThreadsForDelete
    Number of threads that the MDM Hub uses to delete records from the match key tables. Default is
    30
    .
    Configure the block size and the thread counts for the various operations based on the requirements of the MDM Hub environment.

0 COMMENTS

We’d like to hear from you!