W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 2004

RE: A couple of issues...

From: Laird, Brian <BLaird@perseco.com>
Date: Fri, 23 Apr 2004 10:49:30 -0500
Message-ID: <45A6279F82E4CA4BBDC0F4EFC7B6A2FE127FA8@atlas.perseco.com>
To: "Yves Lafon" <ylafon@w3.org>
Cc: <www-jigsaw@w3.org>

Just to confirm: these are tuning the http "client" part of jigsaw.  Correct?

Thanks for all the help.  Those did seem to increase performance.  Is there anyway to disable the caching of connections?  I realize that it is counter intuitive, but my thought is that instead of always trying to get a connection out of the pool, make sure it is still good, and then run something on it.  It might be faster (especially true on high speed networks) to just create the connection every time.

Let me know what you think,
Brian

-----Original Message-----
From: Yves Lafon [mailto:ylafon@w3.org] 
Sent: Friday, April 23, 2004 10:41 AM
To: Laird, Brian
Cc: www-jigsaw@w3.org
Subject: RE: A couple of issues...

On Fri, 23 Apr 2004, Laird, Brian wrote:

> I am trying those now, can you explain them or point me to the docs that
> explain them.  I just want to understand what exactly I am tuning.
Ok, comments inline

>
> Thanks,
> Brian
>
> -----Original Message-----
> From: Yves Lafon [mailto:ylafon@w3.org]
> Sent: Friday, April 23, 2004 9:48 AM
> To: Laird, Brian
> Cc: www-jigsaw@w3.org
> Subject: RE: A couple of issues...
>
> On Fri, 23 Apr 2004, Laird, Brian wrote:
>
> > Yves,
> >
> > Here is my current server configuration.  Let me know if you see
> > anything that should be changed.  In the future, we plan on turning off
> > keep alives because it helps our load balancer better.
>
> Try to add those:
> org.w3c.www.protocol.http.connections.max=50 (maybe more)
The maximum number of simulatenous connections

> org.w3c.www.protocol.http.lenient=true
lenient parsing mode (allow for semi-broken HTTP to go through)

> org.w3c.www.protocol.http.keepbody=false
keepbody is to try to use an idle connection for requests that have an
entity, in some case it might not be practical (ie: to do mark/reset)

> org.w3c.www.protocol.http.connections.timeout=60000
The maximum time waiting on a read for a socket.

> org.w3c.www.protocol.http.connections.connTimeout=5000
The maximum amount of time allowed to attempt a TCP connection

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."


************************************************************************
This e-mail and any accompanying documents or files contain information that is the 
property of Perseco, that is intended solely for those to whom this e-mail is addressed 
(i.e., those identified in the "To" and "Cc" boxes), and that is confidential, proprietary, 
and/or privileged.  If you are not an intended recipient of this e-mail, you are hereby 
notified that any viewing, use, disclosure, forwarding, copying, or distribution of any of 
this information is strictly prohibited and may be subject to legal sanctions.  If you have 
received this e-mail in error, please notify the sender immediately of any unintended 
recipients, and delete the e-mail, all attachments, and all copies of both from your system.

While we have taken reasonable precautions to ensure that any attachments to this e-mail 
have been swept for viruses, we cannot accept liability for any damage sustained as a 
result of software viruses.
************************************************************************
Received on Friday, 23 April 2004 11:49:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:37 GMT