> From: Mike Cronin [mailto:[EMAIL PROTECTED]
> Is there any reason why you would not want to use compression on a
> Connector?
You're trading CPU cycles (running the compression algorithm) for
bandwidth. I suspect you're also trading a certain amount of RAM (some
extra buffers), though I haven't checked or measured how much so I may
be talking out of my hat (as usual). Finally, you may be increasing the
time to the first byte arriving back at the client, as you're increasing
the amount of output the client has to generate before the first segment
of the response is sent. If your servers are CPU-bound, you may not
have the spare cycles; if you're tight on RAM, check whether the
compression increases the memory use. If you have timing requirements,
check that a system with compression enabled still meets them.
All that said, a "typical" business application almost certainly has
spare CPU, some spare RAM and no tight timing constraints on the first
byte being returned - it's generally bandwidth out of the server and
querying the database that are the limiting factors.
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
