On 23/03/2014 12:41, Martin Gainty wrote:
Date: Sat, 22 Mar 2014 14:24:01 -0400
Subject: Effects of turning off sendFile in the NIO connector
From: tomcat.ran...@gmail.com
To: users@tomcat.apache.org
What effect would setting useSendfile=false have on a web application using
the NIO
Date: Sat, 22 Mar 2014 14:24:01 -0400
Subject: Effects of turning off sendFile in the NIO connector
From: tomcat.ran...@gmail.com
To: users@tomcat.apache.org
What effect would setting useSendfile=false have on a web application using
the NIO connector? I'm asking because I may want
MGwhen you enable sendfile support with request attr
org.apache.tomcat.sendfile.support = true
MGYou will need to set these 3 header attributes
org.apache.tomcat.sendfile.filename: Canonical filename of the file which
will be sent as a String
org.apache.tomcat.sendfile.start: Start
On 23/03/2014 19:37, John Smith wrote:
We also only really need compression on XML data, the site has minimal
HTML, SWF's don't really benefit from gzip and some binary data we send
back and forth is already compressed. I could manually implement
compression on XML at the application level
John
The consequences for disabling sendFile are extremely hard to quantify
as there are so many variables. I would normally expect there to be more
CPU load but how much more? No idea. It might be impossible to detect,
it might leaver your CPUs pegged at 100%.
The only way you will know
What effect would setting useSendfile=false have on a web application using
the NIO connector? I'm asking because I may want to use gzip compression in
the connector. The docs state:
*There is a tradeoff between using compression (saving your bandwidth) and
using the sendfile feature (saving your
