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 Performance of Search Requests

Optimizing the Performance of Search Requests

The performance of a search request depends on the RAM of the machine on which you install the MDM Hub components. You must have sufficient operating system disk cache so that you can cache the entire index or the important parts of the index. Do not set a higher Java heap size that might reduce the operating system disk cache. You can also use solid-state disks instead of traditional spinning hard disks for better performance of the search requests.
The scope of a search request increases with the increased number of searchable fields. Multiple searchable fields increase the indexing and searching time, so configure only the required fields as searchable fields. The number of filterable and facet fields can also affect the performance of a search request, so avoid configuring insignificant fields as filterable or facet fields.
Some of the search indexes might become irrelevant when you update the searchable field properties. The irrelevant indexes can affect the performance of the search requests. After you update the searchable field properties, run the Initially Index Smart Search Data batch job to clean the indexes and to achieve improved search performance.
You can also add the following parameters to the JAVA_OPTS variable to improve the performance of the search requests:
solr.autoCommit.maxTime
Number of milliseconds between two hard commit operations. A hard commit operation terminates the transaction log and commits the index changes to the database. A shorter time period impacts the indexing performance. A longer time results in slower Solr startups. Default is 15000.
solr.autoSoftCommit.maxTime
Number of milliseconds between two soft commit operations. A soft commit operation continues to update the transaction log but does not commit the index changes to the database. A search request accesses the updated indexes even though the index changes are not committed to the database.
The value also indicates the minimum time period required for a new or updated business entity to be available for search. A shorter time period reduces the near-real-time window. A longer time period improves the performance of the search requests. Default is 180000.
solr.autoSoftCommit.maxDocs
Maximum number of documents to add before triggering a soft commit operation. A lower number reduces the near-real-time window. A higher number improves the performance of the search requests. Default is 100000.
For more information about the parameters, see the Apache Solr documentation.

0 COMMENTS

We’d like to hear from you!