[imp] Re: Re[4]: IMP 3.2.1 very slow

Jan Schneider jan at horde.org
Fri Apr 25 11:48:13 PDT 2003


Zitat von Michael M Slusarz <slusarz at bigworm.colorado.edu>:

> Quoting Chuck Hagenbuch <chuck at horde.org>:
>
> | Quoting "Abner G. Jacobsen" <abner at integraweb.com.br>:
> |
> | > Using php 4.3.1 with apache2 i solved this problem putting
> | >
> | > echo "\n" ;
> | >
> | > after every header(... int the sources
> |
> | Interesting! There was a while when I had to do this for WAP clients,
> but
> | that wasn't the case during my recent work on MIMP. Can you or anyone
> | else confirm this, say more about it, or explain why it might be
> | necessary?
>
> FWIW, I run PHP 4.3.2RC1 and Apache 2.0.45 and I do not see this problem
> at
> all.  In fact, within the last month I would say that performance has
> improved with HEAD (for IMP, at least, it may be because we handle imap
> connections better in IMP_IMAP:: then we did previously).  So, if this is
> indeed a problem with PHP 4.3.1, it appears to be fixed in the newest
> versions.

The reason might be that the default SAPI for Apache 2 switched to
apache2handler when it was apache2filter in PHP 4.3.1. This SAPI is
(according to what I read on the PHP mailing lists) much more stable and
has a much better performance than the old SAPI.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft


More information about the imp mailing list