[imp] Large attachments timing out.

[Kevin Konowalec]

Hi Jan,

I removed that parameter and got the same results.  We set up 3  
different machines and attempted to download a 14MB attachment on  
each machine simultaneously.  Just before Firefox timed out at the 5  
minute mark this is what top said:

load averages:  2.25,  1.42,   
1.01                                                   10:44:51
72 processes:  3 running, 68 idle, 1 on processor
CPU states: 70.8% user,  0.0% nice, 28.5% system,  0.8% interrupt,   
0.0% idle
Memory: Real: 363M/715M act/tot  Free: 1275M  Swap: 0K/4096M used/tot

   PID USERNAME PRI NICE  SIZE   RES STATE    WAIT     TIME    CPU  
COMMAND
11434 www       	61    	0   93M  101M  run     		 -	0:53      	33.40%  
httpd
30307 www       	63    	0   84M   87M   run      		-       2:14 	 
33.11% httpd
1475   www       	61    	0   73M   83M   run      		-       0:18 	 
29.44% httpd

What's Imp doing that makes apache jump to over 100Mb resident??

Whatever it's doing it's taking a LONG time to do it.  2 users can  
download a 14MB attachment simultaneously in about 3.5 mins.  3 users  
will time out on IE and Firefox (safari must have a longer timeout).   
It takes MUCH longer than downloading the message to the server and  
then downloading from the server to the client should take.  On a  
gigabit connection as we have that whole operation shouldn't take  
more than 30 seconds.  Where's the overhead coming from?  Is there a  
way to optimize this?



On Nov 5, 2006, at 6:55 AM, Jan Schneider wrote:

> Zitat von Kevin Konowalec <webadmin at ualberta.ca>:
>
>> Horde: 3.1.2
>> Imp: H3 (4.1.2)
>> Turba: H3 (2.1.1)
>> PHP 4.4.1
>>
>>
>> Has anyone had problems with Imp taking a VERY long time to  
>> download attachments?  We have been doing some testing and with 3  
>> users downloading large files simultaneously (~14MB each) it takes  
>> in excess of 5 minutes for the file to download.  Safari doesn't  
>> seem to have a problem with this but IE and Firefox both seem to  
>> time out at EXACTLY 5 minutes.  I went into the Firefox  
>> about:config settings and set the two timeouts I could find to  
>> over 300 seconds (300 was the default) and restarted but it still  
>> times out at 5 minutres.
>>
>> In the apache error log I get:
>>
>> [Fri Nov  3 11:30:11 2006] [info] [client xxx.xxx.xxx.xxx] send  
>> timed out
>> [Fri Nov  3 11:30:11 2006] [info] [client xxx.xxx.xxx.xxx] client  
>> stopped connection before rvputs completed
>
> Try removing the strlen($body) parameter from the downloadHeaders()  
> call in imp/view.php's 'save_message' section.
>
> Jan.
>
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> -- 
> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>