On 05/07/2012 06:50 PM, Andy Wang wrote:
On 05/07/2012 06:06 PM, André Warnier wrote:
Considering your setup, it should not be too hard to set up a
download of the same file file directly from Tomcat (through its HTTP
Connector), to compare that with your two previous ways. This way,
you could make sure if it is Tomcat, or the mod_jk/AJP link which is
the issue.
Also, still considering your setup, it should be possible to
configure things so that these file downloads are handled directly by
Apache httpd, since that seems to satisfy your expectations. mod_jk
"JkMount/JkUnMount" rules (*) should make that possible, no ?
Have to be a bit careful not to introduce security holes, and I am
assuming that the files are static (which may be wrong here).
(*) or the <Location ..> + "setHandler jakarta-servlet" configuration
variation
Thanks for the http connector idea. I forgot about that. The primary
reason why i'm using tomcat to download a static file is really for
testing purposes to confirm performance between mod_jk and direct
apache. we have servlets that stream content files that see the same
massive performance hit so in our actual use case it's not static
files :(. I'm thinking this would be a valid test to help at least
tweak mod_jk to it's potential.
We've checked and double checked the buffering code of the servlets
and it all looks fine AND the performance is fine on Linux and the
speed characteristics are identical to serving static files through
tomcat + mod_jk so I'm hoping that it's an apples to apples comparison.
Andy
Through the HTTP connector the performance is similar to apache direct.
30mb/s
So there's something interesting going on specifically ajp.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
