You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page.
Turn on more accessible mode
Turn off more accessible mode
Skip Ribbon Commands
Skip to main content
This page location is:
Data Engineering Integration
Data Engineering Integration
Enterprise Data Catalog
Enterprise Data Lake
Enterprise Data Preparation
Cloud Application Integration
Cloud Data Integration
Cloud Customer 360
Cloud Data Wizard
Informatica Cloud for Amazon AWS
Informatica for Microsoft
Cloud Integration Hub
Cloud B2B Gateway
Cloud API Management
Cloud Data Integration – Elastic
Complex Event Processing
Proactive Healthcare Decision Management
Real-Time Alert Manager
B2B Data Exchange
B2B Data Transformation
Data Integration Hub
Data Validation Option
Data Quality & Governance
Axon Data Governance
Data as a Service
Data Security Group (Formerly ILM)
Data Centric Security
Master Data Management
MDM – Relate 360
MDM Registry Edition
Product Information Management
MDM - Product 360
Ultra Messaging Options
Ultra Messaging Persistence Edition
Ultra Messaging Queuing Edition
Ultra Messaging Streaming Edition
Edge Data Streaming
PAM (Product Availability Matrices)
Informatica Expert Assistant
Velocity (Best Practices)
KB Home Page
Top Link Bar
The distributed search is seen to be slower than the non-distributed search in Relate 360
In Relate 360, the distributed search is a search model that distributes a search request to multiple region servers of the repository and performs the search directly on the region servers.
Distributed search optimally uses the available resources and should result in improved search performance.
However, in earlier versions of Relate 360 (prior to 10.1), it is seen that, instead of increasing performance, enabling the distributed search actually decreases the performance.
This issue occurs due to a design flaw in previous incarnations of the distributed search (DS), which can perform a lot more matches than the non-distributed search (NDS) since a particular candidate record can fall into multiple ranges for the same match-rule/input record.
In NDS, since all the candidates are retrieved at the client-side, the records that have been already matched against the input record can be tracked.
However, in case of DS, since the matching takes place at the region level, the matches that have already been done cannot be tracked, hence the same candidate may be matched multiple times.
From Relate 360 10.1 onwards, the distributed search has been redesigned and additional concurrency features have been added. To resolve the issue of a slowdown in the DS performance, upgrade to Relate 360 10.1.
Last Modified Date:
2/13/2020 2:15 AM
People who viewed this also viewed
Did this KB document help you?
This document resolved my issue
This document did not resolve my issue
This document helped but additional information was required to resolve my issue
What can we do to improve this information (2000 or fewer characters)
© 2016 Informatica All Rights Reserved