RE: [aus-dotnet] Http Compression...

[Mick Badran]

I know we keep talking about 'if you want to compress...then here it is...'

BUT

'...dont do it as CPU will increase etc etc etc.'

 

Does anyone have any perf numbers on this? Happy just to see any (in case you guess...I'm hooked on 'Myth Busters' - how many things do they blow up!)

(as I understand, the compression details came in IIS 4.0 + http standards when CPUs werent half the 'men' of what they are today)

 

The reason why I'm curious is that under IIS - we get the IIS Compressed Files folder where our static/cached page output will live ready to be shot down over the wire.

 

Given the huge gains of compressing text, this keeps the wire pretty lean.

 

Any thoughts fellow mythbusters??

---

From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of Joseph Cooney
Sent: Tuesday, 5 July 2005 10:54 AM
To: dotnet@xxxxxxxxxxx
Subject: Re: [aus-dotnet] Http Compression...

AFAIK Http Compression is just a matter of setting the appropriate 
parameter in the HTTP header http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html 
and then compressing the output stream in the manner which you've indicated in 
the header. It is not in any way limited to IIS 6. By doing this you're 
effectively trading off increased server CPU utilization and possibly increased 
latency for decreased network traffic.

Joseph

On 7/5/05, Donald <donald.w.chow@xxxxxxxxx> wrote:

The following link shows a good step by step method on how to turn on IIS 6.0 compression.
http://www.dotnetjunkies.com/HowTo/16267D49-4C6E-4063-AB12-853761D31E66.dcik

Don


On 05/07/05, list@xxxxxxxxxxxxxxx < list@xxxxxxxxxxxxxxx> wrote:

Anyone have any free resources on http compression...did not realise that broswers support compression...   I want to compress most of my pages in asp.net 1.1 if possible....   AnthonyS