the reduction depends on your html right? if you use a lot of tables, you're likely to see 5-10x compression. The easiest trick is to save a couple of your biggest pages and zip them up. Compare the file size. Now, if you have regular log reports, you can see which pages get requested the most and how many bytes it is. from that you can get a fairly accurate estimate in total bytes sent per week/month. Stripping out carriage returns and tabs most likely won't give you as much as compression. Here is an easy way to test it on other sites. Load a site that uses gzip with a browser that support gzip and without. Compare the actual bytes sent and how much faster the page loads. I know from first hand experience verizon SuperPages reduced 60K+ to 6K when they started using compression. The user's perception is the page was 2-4x faster. peter lin
John Sidney-Woollett <[EMAIL PROTECTED]> wrote: Peter Lin said: > have you tried turning gzip compression? that should produce similar > bandwidth savings to stripping out extra carraige returns and double > spaces. We running Apache 1.3.x + JK + TC 5.0.x What's better the gzip valve/filter in Tomcat, or try doing the compression with an Apache module (if that's even possible for JSP rendered pages)? Also, is there a threshold below which the penalty for processing the compression outweighs the data payload reductuion? We want to be low bandwidth + responsive... > you could always use the jasper plugin architecture to strip out excess > stuff Is there a link to some docs for this? Thanks John Sidney-Woollett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster.
