Need to improve performance of the MDm System

[Former Member]

Hi SDNers Experts,

I am searching for performance techniques to improve performance through ABAP APIs.

In my repository I am having 3 million records. And I am using Startegy to Match and Merge. Startegy is of with combination of 4 fields. When I tried to execute this startegy combination of 4 fields means in Data Manager it will search for 4 times (3 * 4 = 12 millions times) correct me If I am wrong. I will run this startegy through ABAP APIs from CRM system. To excute this it is taking so much of time and some times an error will occur "CONNECTION TIMED OUT".

Is there anyway to reduce time taking to excute the startegy through ABAP APIs.

Is there any way to improve performance by creating Masks of that particluar Repository or anything program written within MDM like in Data Managager to improve performance.

Thanks

Kiran

[Former Member]

I got the solution my self

[former_member189669]

Hi Kiran,

Please ensure the below and you will notice the performance improvement.

1. Enable sort index to Normal for those fields which are used in Matching rule.

If you are using a look up field (like country), enable sort index at both maintable and lookup table (display field) level.$

Sort indices has a very powerful impact on matching performance.

2 .Choose a field which is a part of matching rules based on which you can funnel entire set of records. You may also have 2 layers of such funneling.

eg. Choose all records out of 3million which belong to Country India (Country Code 0 IN).

3. After funnening the records (user search), trigger matching strategy to compare your new record with the results of search.

Matching >Selected Vs Results.

Let me know if you need any more clarification.

Regards,

Vinay

[former_member218126]

Hi ,

There is a need to review existing matching strategy amd optimize it so that it should match as less records as possible like by applying some more filters to reduce the number of records available for matching.

You can refer below link to optimize your matching strategy in data manager.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/408b8031-6fc4-2b10-c18b-a77abefb75b9

Hope this is helpful.

Regards,

Vineet

[Former Member]

Hello Kiran

In sap mdm 7.1 included many parameters for improve it productivity.

Check some parameters in your mds.ini file:

"Client Ping Timeout Minutes" -

Number. Causes MDM Data Manager to send a

ping to the Master Data Server after the specified

number of minutes of inactivity. Use to keep the

socket connection active on networks where inactive

sockets are killed by the system. Default is 0 (no

pings). See also Inactive Client Timeout.

"Inactive Client Timeout Minutes" -

Number. Minutes of inactivity to allow from a client

(MDM application, API, service, etc.) before the

Master Data Server starts sending ping packets to

the client. Used to clean up dead connections on

networks which kill inactive sockets. If the

connection is alive, the pings succeed and nothing

else happens. If the connection is dead, the ping

attempts ultimately fail and the network informs the

Master Data Server that the connection is dead.

Default is 0 (disabled). See also Client Ping

Timeout Minutes.

and

"Multi-threaded Matching" -

True/False. Whether to enable multi-threading for

record matching tasks. Maximum number of threads

is governed by the Max Threads Per

Operation parameter.

more about mds.ini configuration you can found here:

http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/content.htm

Regards

Kanstantsin Chernichenka