I post this a couple og month ago, but didn't receive any reply, so as keep getting this error I'm posting again in case someone can give me a little help on this:
We have several users that report slowness working on Outlook using the KOFF connector, for example, when they change from one folder to another the outlook freeze with "Not Responding" for a couple of minutes, sometimes this happen when they send or opened an email. We have about 305 users, Kerio Connect runs on Debian 7, and a RAID 10 array with 8 600GB disk at 15K RPM (the server is a PowerEdge R710). This happens with users with a mailbox between the 6 and 12 GB, we try to keep mailbox folders (inbox, sent items, etc,) below the 10K items.
I thought maybe this could be happening because of the disks on the server, maybe needs more disks to make the disk system faster, but when we install an SSD disk on a client computer, the problem get solved and the user can work without any problem withOutlook, even with mailboxes as large as 25GB. This made me think maybe the problem is not on the server, but as you may know, we can't install SSD to all computers.
So, what can be causing this slowness? As far as I know, Outlook users working with the offline connector should contact the server only to synchronize with the server right? so the Outlook should be talking with the local cache most of the time right? Is this the reason why the SSD disk improve Outlook performance? But what about non-ssd computers? What else should I check?
Thanks and best regards,
- Bud Durland
You've got the server piece pretty well covered, so the next step is client side. Basically, the off-line cache is a database; the KOFF software is a database server. (overly simplified, but enough for our purpose here).
To improve speed on the client, the primary factors are RAM and local storage. We find that anyone with a mail store > 1GB will see significant improvement by running a 64bit OS and at least 8GB of RAM. Installing SSD also makes a significant contribution. Ideally, you'll have both, but if you have to pick on over the other, do the RAM first.
Finally, another option is to not use OutLook. I use eMClient with our Kerio connect server and it works very well. Calendars & contact sync, etc. The only thing I can't do with eMClient that I can do with OutLook is work with global contact groups (which are also kinda kludgy in OutLook). Users groups with e-mail addresses work just fine.
Kerio discussion forums are intended for open communication between forum
members and may contain information and material posted by members which may
be useful in learning about Kerio products. The discussion forums are not
intended to provide technical support for any specific product. Any
information implied or expressed in the discussion forums is that of the
posting member. Kerio is in no way responsible for the information posted in
the forums, or its accuracy. Kerio employees may participate in the
discussions, but their postings do not represent an offical position of the
company on any issues raised or discussed. Kerio reserves the right to
monitor and maintain the forums to promote free and accurate exchange of