/ Zope / Apsis / Pound Mailing List / Archive / 2004 / 2004-07 / Odd problem - lingering short packets?

[ << ] [ >> ]

[ [MailServer Notification]To Recipient virus found ... ] [ Server error 500 - response error read from ... / ... ]

Odd problem - lingering short packets?
Russ Ferriday <russf(at)topia.com>
2004-07-27 17:09:25 [ SNIP ]
Hello,

Kudos to apsis for Pound. I like the single-mindedness-of-purpose and 
ease of configuration.

I have an interesting situation and I welcome your thoughts.

I've been tcpdumping on either side of pound and at my browser and 
suspect that I can see short packets lingering in pound for about 30 
seconds on their way back to the browser. When I direct requests direct 
to Zope, I do not have the problem, and when I clear the cache in the 
client, so that packets are no longer 250 byte 'HTTP/1.1 304 Not 
Modified' packets, and go through pound, I also have no problem.

I have data for all this. What's the best way to dialog and sanity 
check my thoughts?

--r
—————————————————————
Russ Ferriday
Solution Workshops for Plone
(+44) (0) 7789 338868
http://www.solutionworkshops.com


Re: Odd problem - lingering short packets?
Robert Segall <roseg(at)apsis.ch>
2004-07-27 17:25:24 [ SNIP ]
On Tuesday 27 July 2004 17.09, Russ Ferriday wrote:
> Hello,
>
> Kudos to apsis for Pound. I like the single-mindedness-of-purpose and
> ease of configuration.
>
> I have an interesting situation and I welcome your thoughts.
>
> I've been tcpdumping on either side of pound and at my browser and
> suspect that I can see short packets lingering in pound for about 30
> seconds on their way back to the browser. When I direct requests direct
> to Zope, I do not have the problem, and when I clear the cache in the
> client, so that packets are no longer 250 byte 'HTTP/1.1 304 Not
> Modified' packets, and go through pound, I also have no problem.
>
> I have data for all this. What's the best way to dialog and sanity
> check my thoughts?
>
> --r
> —————————————————————
> Russ Ferriday

Are you using the latest -current? It should fix this problem, as it now 
flushed the queues more often.

You could also set your Client and Server timeouts to lower values so that 
Pound knows when the other side is done sending stuff.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-1-920 4904

Re: Odd problem - lingering short packets?
Russ Ferriday <russf(at)topia.com>
2004-07-27 18:28:13 [ SNIP ]
Thanks Robert!

On 27 Jul 2004, at 16:25, Robert Segall wrote:

> Are you using the latest -current? It should fix this problem, as it 
> now
> flushed the queues more often.
No - building it now. was on 1.7 released.

> You could also set your Client and Server timeouts to lower values so 
> that
> Pound knows when the other side is done sending stuff.
I need to set Server high (30 secs) to allow for startup time, when 
first page might take that long (OK, may be better, now that we have 
ZEO caches working properly. Perhaps I could say 10 seconds but that 
would still look really bad.)

I'm building on OSX Panther 10.3 and get:

gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
-D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o pound.o pound.c
gcc: unrecognized option `-pthread'
gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
-D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o http.o http.c
gcc: unrecognized option `-pthread'
gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
-D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o config.o 
config.c
gcc: unrecognized option `-pthread'
gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
-D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o svc.o svc.c
gcc: unrecognized option `-pthread'
gcc  -pthread -o pound pound.o http.o config.o svc.o -lssl -lcrypto 
-ldl  -lpthread
gcc: unrecognized option `-pthread'
I'll send you the makefile separately. I'll go ahead with a trial and 
report.

--r.
> -- 
> Robert Segall
> Apsis GmbH
> Postfach, Uetikon am See, CH-8707
> Tel: +41-1-920 4904
>
—————————————————————
Russ Ferriday
Solution Workshops for Plone
(+44) (0) 7789 338868
http://www.solutionworkshops.com


Re: Odd problem - lingering short packets?
Russ Ferriday <russf(at)topia.com>
2004-07-27 19:20:35 [ SNIP ]
Just confirming. Current does work, on Panther.
I ignored the warnings below, and removed -D options in make install, 
and put in some real groups - bin not being defined in OSX.
Thanks for your quick response.
--r
On 27 Jul 2004, at 17:28, Russ Ferriday wrote:

> Thanks Robert!
>
> On 27 Jul 2004, at 16:25, Robert Segall wrote:
>
>> Are you using the latest -current? It should fix this problem, as it 
>> now
>> flushed the queues more often.
> No - building it now. was on 1.7 released.
>
>> You could also set your Client and Server timeouts to lower values so 
>> that
>> Pound knows when the other side is done sending stuff.
> I need to set Server high (30 secs) to allow for startup time, when 
> first page might take that long (OK, may be better, now that we have 
> ZEO caches working properly. Perhaps I could say 10 seconds but that 
> would still look really bad.)
>
> I'm building on OSX Panther 10.3 and get:
>
> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o pound.o 
> pound.c
> gcc: unrecognized option `-pthread'
> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o http.o http.c
> gcc: unrecognized option `-pthread'
> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o config.o 
> config.c
> gcc: unrecognized option `-pthread'
> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o svc.o svc.c
> gcc: unrecognized option `-pthread'
> gcc  -pthread -o pound pound.o http.o config.o svc.o -lssl -lcrypto 
> -ldl  -lpthread
> gcc: unrecognized option `-pthread'
> I'll send you the makefile separately. I'll go ahead with a trial and 
> report.
>
> --r.
>> -- 
>> Robert Segall
>> Apsis GmbH
>> Postfach, Uetikon am See, CH-8707
>> Tel: +41-1-920 4904
>>
> —————————————————————
> Russ Ferriday
> Solution Workshops for Plone
> (+44) (0) 7789 338868
> http://www.solutionworkshops.com
>
—————————————————————
Russ Ferriday
Solution Workshops for Plone
(+44) (0) 7789 338868
http://www.solutionworkshops.com


Re: Odd problem - lingering short packets?
Russ Ferriday <russf(at)topia.com>
2004-07-27 19:36:35 [ SNIP ]
So, this change has improved things by a factor of 4. Now it just takes 
20 seconds to load those pages that earlier took 80 seconds.

I'm not excited about it, but if another round of tcpdump traces would 
help see where the time is going, you just need to say. My last set did 
show up a 30 sec lag for those short packets.

I'd have to work into the code to help there, but the problem seemed to 
be that pound received a short packet for the browser, was slow to 
notice, thus delaying sending to browser and closing the connection. 
Holding the browser in an almost frozen state.

Gotta say, this change may have prevented me needing switch to apache 
for a while. That's a bonus! Thanks.
--r.

On 27 Jul 2004, at 18:20, Russ Ferriday wrote:

> Just confirming. Current does work, on Panther.
> I ignored the warnings below, and removed -D options in make install, 
> and put in some real groups - bin not being defined in OSX.
> Thanks for your quick response.
> --r
> On 27 Jul 2004, at 17:28, Russ Ferriday wrote:
>
>> Thanks Robert!
>>
>> On 27 Jul 2004, at 16:25, Robert Segall wrote:
>>
>>> Are you using the latest -current? It should fix this problem, as it 
>>> now
>>> flushed the queues more often.
>> No - building it now. was on 1.7 released.
>>
>>> You could also set your Client and Server timeouts to lower values 
>>> so that
>>> Pound knows when the other side is done sending stuff.
>> I need to set Server high (30 secs) to allow for startup time, when 
>> first page might take that long (OK, may be better, now that we have 
>> ZEO caches working properly. Perhaps I could say 10 seconds but that 
>> would still look really bad.)
>>
>> I'm building on OSX Panther 10.3 and get:
>>
>> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
>> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o pound.o 
>> pound.c
>> gcc: unrecognized option `-pthread'
>> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
>> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o http.o http.c
>> gcc: unrecognized option `-pthread'
>> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
>> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o config.o 
>> config.c
>> gcc: unrecognized option `-pthread'
>> gcc -DF_CONF=\"/usr/local/etc/pound.cfg\" -g -O2 -DAEMON -DUPER  
>> -D_REENTRANT -pthread -Wstrict-prototypes -pipe   -c -o svc.o svc.c
>> gcc: unrecognized option `-pthread'
>> gcc  -pthread -o pound pound.o http.o config.o svc.o -lssl -lcrypto 
>> -ldl  -lpthread
>> gcc: unrecognized option `-pthread'
>> I'll send you the makefile separately. I'll go ahead with a trial and 
>> report.
>>
>> --r.
>>> -- 
>>> Robert Segall
>>> Apsis GmbH
>>> Postfach, Uetikon am See, CH-8707
>>> Tel: +41-1-920 4904
>>>
>> —————————————————————
>> Russ Ferriday
>> Solution Workshops for Plone
>> (+44) (0) 7789 338868
>> http://www.solutionworkshops.com
>>
> —————————————————————
> Russ Ferriday
> Solution Workshops for Plone
> (+44) (0) 7789 338868
> http://www.solutionworkshops.com
>
—————————————————————
Russ Ferriday
Solution Workshops for Plone
(+44) (0) 7789 338868
http://www.solutionworkshops.com


MailBoxer