Discussion:
Running the TDI Update in a multi threaded way or improve the performance
Add Reply
Khajan Joshi
2017-10-02 07:34:01 UTC
Reply
Permalink
Raw Message
Hi ,
We had a JNDI connector that updates the users in ISIM. The ldap connector is used as a feed and in a iterator mode. Is there a possible way to enhance the performance with some configuration changes as i see the request to ISIM are coming one by one (gap of 1 sec) which makes sense as it iterates. Can somehow this be multithreaded and dump a batch of updates to ISIM. I am looking and working on this but wanted to check also if somebody has tweaked or configured it like that.
Franzw
2017-10-02 10:46:13 UTC
Reply
Permalink
Raw Message
Post by Khajan Joshi
Hi ,
We had a JNDI connector that updates the users in ISIM. The ldap connector is used as a feed and in a iterator mode. Is there a possible way to enhance the performance with some configuration changes as i see the request to ISIM are coming one by one (gap of 1 sec) which makes sense as it iterates. Can somehow this be multithreaded and dump a batch of updates to ISIM. I am looking and working on this but wanted to check also if somebody has tweaked or configured it like that.
I would take a look into the ISIM server ibmslapd.log and check whether some attributes are not indexed...

It sounds like your ISIM system is not tuned as well as it should be or is lacking resources. In that case any multi-processing will not help you.

Download the ISIM performance tuning guide from IBM Support and ensure your system is properly tuned - then many things should run better...

HTH
Regards
Franz Wolfhagen
yn2000
2017-10-02 15:46:02 UTC
Reply
Permalink
Raw Message
"..the request to ISIM are coming one by one (gap of 1 sec) which makes sense as it iterates.." Nope. It does not make sense.

A solid 1 second gap is very rare. The only possibility that this condition could happen is the fact that you have system.sleep(1); command in your AL, which basically delay the TDI process... by design. People do add a sleep command if they know that the input (data source) is transactional type of data source, where there is a possible two updates (e.g. one update phone, the other update the address) of the same user on the same iteration. So, adding sleep command will reduce the chance to have a race condition within the ISIM system.

Technically, yes, you can find many ways to do multithreading on TDI system, but based on my experience, people tend to slow down on TDI processing, rather than speeding it up.

Having said, if this is found to be ISIM issue, then follow what Mr. Franz said. The statement that makes me wonder is the solid 1 second gap, as a not fine-tuned ISIM would generate a more disperse outcome rather than a solid 1 second gap.

just food for thought.
Rgds. YN.
Khajan Joshi
2017-10-02 18:35:28 UTC
Reply
Permalink
Raw Message
Thanks YN for the input and food for thought. I will look into the parameters and way to tune ISIM one by one and let you know the results. Appreciate the inputs
Khajan Joshi
2017-10-02 18:31:57 UTC
Reply
Permalink
Raw Message
Thanks for the insight Franz, I will look into this and update with my findings. Your guidance is appreciated
Loading...