Slow Response Time of Opening Web Page with LDAP

HCL Domino Domino Forum
1

Hi,

I have some problem related to the response time. Following is the scenario:

  1. Previously I was having Lotus 6.5.4 with normal authentication of the user with names.nsf.

  2. Now the new lotus server R8.0.1 has been installed and the LDAP user authentication has been activated.

  3. The LDAP has been connected to the AD so the the user’s password authentication will be validated through the Windows Active Directory for SSO.

  4. The Windows Server version is 2003.

Now the problem is:

  1. When there is no LDAP configuration is active on the Lotus Server R 8.0.1, the response time of all the applications previously built in Lotus R6.5.4 is good.

  2. But when the LDAP authentication to use AD is active following happens:

  • When the user logs in to the application, the reposnse time is good and it opens within a second.

  • But when the user opens any form which contains a few DBLookups and have some data, it takes more than 10 seconds in opening. Previously it was taking only 2-4 seconds when the LDAP was not active.

Please suggest me what to do?

Thanks,

Atin Gupta

Team Lead, Lotus Notes

Velocis Systems Pvt LTD

9810707414

2

Subject: Performance considerations when authenticating against Active Directory

Performance considerations when authenticating against Active Directory

Maybe this will help.

Hans

3

Subject: trace, network involvement, and rewriting…

The first thing I would do would be, from one of the clients with the problem, do a trace from the notes client (File>Preferences>Network Ports) to the server the dblookup would be on. Watch to see where the slowness occurs, and/or if there are any errors. If so, you’ll know what to address.

You should consider that if you are using the AD to authenticate, you are adding another step, another network connection, to the process. This can slow things down - especially if any network connection or server in that step is slow or very busy.

If you can’t fix the slowness on the network/authentication side, there are ways to rewrite applications to improve performance on dblookups. Specifically, using the “cache” option, or placing the lookup behind a button (so that it only evaluates when the user presses it, not when the document opens).

4

Subject: Web agents are executing after long delay in LDAP authentication

We have tested all these and identified the cause of problem.When agent are running from Web Page while LDAP is active,it is executing after long delay.

E.g.

We had created one agent and executed it in web page using LDAP authentication and it started after 45 seconds. When we tried executing it after stopping DA(LDAP), it was running within 2 seconds.