Steffen Heil said: > I cannot help you on this, but you should realise, that if you archive to > reduce you jsps output by 10%, this will affect you traffic only by about > 2%. > > We do have a server, which generated (according to access_log_*) > 2.183.339.056 byte in 261.018 requests. But out provider counted about 9GB > of traffic. [Actually he is accounting on switch port level and therefor > including even ARP-requests, but anyway a lot of this traffic is based on > out tomcat server.]
That's a good point - we're also charged at the switch port level! We have a traffic shaper so we can control the amount of bandwidth (Mbit/sec) we use for outbound traffic, and we're trying to cram as much data per second as we can within our (managed/shaped) limit. In fact it seems that (gzip) compression is a better strategy for HTML/CSS pages because it offers compression of 80%. But it's still better to compress the pages after you strip the whitespace for a small final text size. Unfortunately we also have a lot of graphics (but at least once they are cached by the browser) then we only have to deal with a HEAD request to see if they have been updated... Thanks for the feedback. John Sidney-Woollett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
