Hmmmm.... Looks like the majority of sent bandwidth is html, not image files >> ratio is at least 10:1 html to images.
With that in mind, setting zlib compression to ON seems the way to go. Question is, how to implement compression? Is it enough to just ini_set() zlib compression to ON? i.e. will all content be automatically be compressed, or do I need to ob_start() & ob_end_clean() at the start and end of each page? TIA for any clues -- I'm obviously confused about compression techniques..... --Noah "Rush" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > "Cf High" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Having a good problem -- our hockey report site has jumped from 10 > > gigs/month to 30+ gigs/month & growing. > > > > We're getting killed in bandwidth fees at the moment; barring switching to > > another host, will utilizing ZLIB compression significantly reduce > > bandwidth? > > well it depends what uses most of your bandwith. If it is for images, then > compression will not help much since images are allready compressed. In that > case, you may save much more if you can put images in some directory and > tell apache to allow cacheing for that directory. > > On the other hand if your bandwith goes mainly on thransfer of html source > for the pages then compression can shave up to 80% of your bandwith usage. > > rush > -- > http://www.templatetamer.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
