[imp] IMAP recommendations anyone?

[Chris H.]

Hello, and thank you for your reply.
Indeed your suggestion would help. Imp/ Horde also already offer
the same ability to cache the tree and recent messages. However,
there are 2 (well maybe 3) things that bother me about all this:
1) as I mentioned before, 3.09 was about 4-5 times faster. So
why the sudden loss in performance and speed? - not to mention the
additional loads I'm seeing on the CPU's. Top is showing some
really high numbers by comparison, and this is a DUAL CPU box.
2)It still will take about 3-5 minutes to get completely logged
on and the entire message list with only on user logged on and
no other proccess other than MySQL, Apache, Horde/ Imp. 5 minutes.
That's *way* too long, and this is on a dual CPU box with 3Gig of
RAM. Something's *definately* wrong.
So I am going to walk down the list of possibilities to discover
the culprit. Starting with UW-IMAP. I'll probably start by testing
Dovecot. It is reported to be quite a bit faster than UW-IMAP. But
what I most look forward to; is the ability to have much easier
configuration. As with UW-IMAP, it's always a matter of hacking
the source. Anyway, I hope to find that it's the IMAP server (UW)
and not the slight change in direction Horde/ Imp have made.

Thanks again for your response.

--Chris H.


Quoting robert sand <rsand at duluth.umn.edu>:

> Chris,
>
> Have you looked at using a product like imapproxy?  This product 
> keeps stat information about a users connection to an imap server 
> keeping the connection open.  There are issues with imap having to 
> create and destroy a connection every time the user updates their 
> inbox window, reads a message, or does anything that requires a 
> connection to the imap server.  Imapproxy will speed this up by 
> caching the connections and reusing them so that the imap client does 
> not have to keep building and destroying the connection.  We use it 
> here and found an immediate speedup in connections to the imap 
> servers.
>
> Chris H. wrote:
>> Hello all,
>> I was recently able to get a stubborn installation of h-3.11+imp-4.1
>> completed. This was _technically_ a upgrade attempt from h-3.09. However,
>> as I am using MySQL to contain everything. I simply backed up the DB
>> and did a delete-all-old-installs and start a fresh install of 3.11+4.1.
>> Anyway, now that everything is working, it is about 5-7 times slower than
>> the 3.09 install was. So, as I am quite sure it is IMAP server related:
>> more precicely; UW-IMAP related, I was was hoping to solicit some
>> recommendations/ experiences from everyone on the list. I've enjoyed
>> UW-IMAP all these years because it has been well supported and I'm familiar
>> with it's many quirks. But as time goes by, it becomes increasingly
>> difficult to configure (HACK the source) it. So I am hoping that those
>> whom are familiar with the other implimentations of IMAP servers (Cyrus,
>> Dovecot, etc...) might share their experiences with them here. The output
>> would also make a great contribution to IMP/ Horde documentation. :)
>> Anyway, I eagerly await any and all comments. :)
>>
>> Thank you for all your consideration.
>>
>> --Chris H.
>>
>> P.S. This install is on a FreeBSD server.
>>
>
> -- 
> Robert Sand.
> mailto:rsand at d.umn.edu
> University of Minnesota, Duluth
> Information Technology Systems and Services
> 144 MWAH
> 218-726-6122        fax 218-726-7674
>
> "Walk behind me I may not lead, Walk in front of me I may not follow,
> Walk beside me and we walk together"  UTE Tribal proverb.
>



-- 
Shameless self-promotion follows...
... or does it?


-----------------------------------------------------------------
FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006
/////////////////////////////////////////////////////////////////

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: PGP Digital Signature
Url : http://lists.horde.org/archives/imp/attachments/20060427/6add9519/attachment-0001.bin