Hi there,
For those of you who have moved to Zimbra 6, or are testing it, I wonder if any of you have encountered performance problems, specifically during login of the web client?
We are testing Zimbra 6(.0.5) in an environment that uses data that's been cloned from our production 5.0.18 system. The test environment is on a set of VMs. We've noticed very long delays for some users during login - so long in fact that Nginx usually times out and throws up a blank page. For a few users, login never works - it always times out. Before the upgrade to 6, the user can login fine. We've tried:
- increasing resources to the VMs (now sitting at 4 CPUs and 16gb ram each - no change)
- accessing the account using zmmailbox - same timeouts occur
- deleting all shared and remote calendars (had to do this directly in mysql because zmmailbox times out)
- checking for the Zimbra desktop 1.0 "archive flag"
- enabling virtually all debug-level logging for a slow user.
That last one, done this afternoon, showed extremely high ldap activity during login. It appeared to be fetching the user's distribution lists from ldap, repeatedly (for 11 minutes(!)). So we removed the user from every distribution list and restarted mailboxd. Yet still it seemed to fetch them
At this point, this is a show-stoppper for us going to 6.0, so we'll be opening a Support case with Zimbra. But I just thought I'd post here to see if anyone else has seen anything similar
(by the way, even for users who don't suffer the 'login of death', we still notice much longer login times. It seems Zimbra has reverted to instantiating the calendar data at login time, rather than waiting until the Calendar tab is selected. There seems to be a lot more server-side activity in general before the post-login splash page appears)