Performance Stats

[Former Member]

Hi,

We are importing Business partners into MDM. Can we have some stats from experienced folks?

Its taking approx 20 mins for a file containing 5000 BPs - is it the expected output? We have gone through Performance documentation available and have made a few tweaks but found that standard settings work best.

Regards,

Dev.

[Former Member]

Hi Dev,

Here are a few more pointers to help speed-up the import:

1. Kindly check the availble disk space on whivh the database is installed. If Unix, you can set the memory to unlimited for a particular user.

2. If there is any Qualified Look up table {multi-valued], then import the look up values for the corresponding tables first and then import the records. Refreshing look-up values takes lots of time while importing. Hence, to avoid this,Look up values can be imported first and then values can be Auto-mapped in the second import.

3. Normally, we tend to use "Keyword Search" for every field. This reduces the performance. So, you can review this in your data model.

Hope these pointers help.

Regards,

Ritam.

[Former Member]

Hi Dev,

Here are a few more pointers to help speed-up the import:

1. Kindly check the availble disk space on whivh the database is installed. If Unix, you can set the memory to unlimited for a particular user.

2. If there is any Qualified Look up table {multi-valued], then import the look up values for the corresponding tables first and then import the records. Refreshing look-up values takes lots of time while importing. Hence, to avoid this,Look up values can be imported first and then values can be Auto-mapped in the second import.

3. Normally, we tend to use "Keyword Search" for every field. This reduces the performance. So, you can review this in your data model.

Hope these pointers help.

Regards,

Ritam.

[former_member189669]

Hi Dev,

Please let us know if you are importing manually or using MDIS.

In general, import performance depends on multiple factors -

1) Data model of your repository

2) Use of remote keys - ideally remote keys must be used economically.

3) Data load (chunk size)

4) Memory size .

Assuming moderately complex datamodel of your repository, importing 5K records in 20mins seems alright and can be acceptable.

Regards,

Vinay M.S