cancel
Showing results for 
Search instead for 
Did you mean: 

Performace issue - with Matching via ABAP API

Former Member
0 Kudos

Hi Folks,

We are attempting a massive matching via MDM ABAP API - in the order of 100K records vs 500K records. The sever seems to hang forever.

We have tried several things and now running out of time. Does anyone have any bright ideas to make this happen ?

running it on a 4 cpu, 16GB shared memory server. Matching strategy is only for one field with numereous required transformations.

Vinay

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Vinay,

The Three Major factors that affect the performance during Matching in MDM are:

1) Transformations

2) Rules

3) Number of Records

The number of fields you use for finding duplicates and the number of potential dupliacte records are reasons for poor perfromance in Matching within MDM,however the major contributor to this is the transformations that you run for in this case you will need to use tken equals instead of only equals which will futher slow down the process.

An alternate could be if you can perform some standardization on the records before passing them through the MDM strategy either through some third party tool or manually then it could help.Increasing the MDM configurations like the RAM and CPU speed will help but not much untill you control it at the transformations level.

Hope It Helped,

Thanks & Regards

Simona Pinto

Former Member
0 Kudos

Thanks folks - we've changed to "Equals" and split the record for the matching . The server still hangs .. still don't know why.

Former Member
0 Kudos

This issue turned out tobe a bug - which SAP provided a hot fix. Things are far better now .. Thanks for your replies

Former Member
0 Kudos

Hi Vinay

NOrmally trnsformations are the speed breakers in Matching strategy. Try to do away with some of the transformations and I am sure performance of Matching strategy will increase.

Some of the transformations can be taken care by assignment statements OR while importing the data in import Manager.

Also use Equals instead of token equals wherever possible.

We also faced this problem and used the above approach and this helped.

Regards

Ravi