Optimizing Mailing Lists with Direct LDAP

Hey all,

I've noticed performance issues with iMS 5.2p1 (with iDS 5.1) with respect to direct LDAP look up's, especially for large mailing lists. Even a 28 user list takes 10 minutes, where as with MS 4.1.5 it was practaically instance. We also have a dynamic group with everyone (4000 people or so) and it simply pegs the LDAP server @100% CPU and sits there for a day. It seems that there are a ton of ways to optimize the caches and LDAP lookups. Where should I start or what should I do? What settings should I look to fix on the LDAP server, IMTA, etc. to speed things up?

Thanks!

Chris

[625 byte] By [705693] at [2007-11-25 8:38:51]
# 1

This was an LDAP server optimization issue. I increased the memory for both the slapd cache and the database cache. I then added indexes for all the common items search for by the IMTA. I was watching the slapd access logs and saw that the IMTA searchs for a lot of imortant items that are not indexed by default. I added indexes for:

inetUserStatus

mailUserStatus

inetMailGroupStatus

mailEquivalentAddress

mailRoutingAddress

mailMsgMaxBlocks

mailQuota

mailMsgQuota

mailProgramDeliveryInfo

mailDeliveryFileURL

maildeliveryfile

mailConversionTag

mailDeliveryOption

vacationStartDate

vacationEndDate

mailForwardingAddress

memberURL

rfc822mailmember

mailAccessDomain

mailMessageStore

preferredLanguage

mailAllowedServiceAccess

Now a message to everyone that took 24 hours and never went through takes just over a minute to get to 4000 users on my little test server. Smaller dynamic lists are even faster. General performance of message delivery is also faster, as is SMTP response from the client prespective.

705693 at 2007-7-1 15:15:19 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2
what is your critaria for indexing these attibute ?equal .?... ?...?Thanks
708700 at 2007-7-1 15:15:19 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...