Value mapping performance using LookUp API

[Former Member]

All,

We are using Value mapping look up from an external table using JDBC adapter and Lookup API. The scenario works good, but the performance is a hit for us as it is taking 7 seconds for the first step and the subsequent steps are taking much longer. In the performance header it shows that the steps "DB ENTRY QUEUING" and "DB SPLITTER QUEUING" are taking 90% of the time even though mapping execution is real quick.

We tried the below things which did not help us analyze or isolate the problem.

1. We increased the number of dialog processes from 3 to 8. (Optimal value should be 5)

2. We tested the scenario using Value mapping in ID instead of external table. But it is almost taking the same time in the above two steps mentioned.

I would like to know whether any kind of configuration settings to be done on the server like "specifying connection pool capabilities" etc...

Any pointers would be really appreciated.

Thanks and Regards,

GP

[Former Member · Accepted solution]

Hi -

Check the XI Performance Guide attached to NOTE-894509. Sections 4.4.2 and 4.4.3 has some things you can look at for long DB ENTRY QUEUING" and "DB SPLITTER QUEUING" processing times.

Regards,

Jin

[Former Member]

Hi,

Have you seen this weblogs by Prasad recently:

/people/prasad.illapani/blog/2007/03/08/performance-tuning-checks-in-sap-exchange-infrastructure

/people/prasad.illapani/blog/2007/04/20/performance-tuning-checks-in-sap-exchange-infrastructurexi-part-ii

Also are you doing multiple lookups or a single lookup? If you are using multiple lookup for multiple fields which has the same logic then try to use global variables.

---Satish