Is DNN's compression just a switch for IIS's compression and is it it's own implementation?

Anyone noticing a big ifference in performance when compression is turned on?

Salama:

The answer to your first question is no.  DNN can do compression at the application level (ASP.Net) and it is a separate function from the IIS compression, although the end result is basically the same, to send less data to the user's browser.

In my opinion, and my recommendation, is to do compression with IIS if you have control of your own server.  But many in hosted environments don't have this kind of access.  It is for this reason that DNN offers that feature at the application level.

And to answer your second question, you can judge by yourself using a tool like the one in this site (click on the Compression tab next to Security and enter a URL).  It analyzes the content of what the Web server sends to a client and will tell you the compression ratio.   The main page of www.dotnetnuke.com compresses 76%. 

Carlos

IIS compression can be set at the site or folder level.

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/502ef631-3695-4616-b268-cbe7cf1351ce.mspx?mfr=true

More control using a third party product:

http://www.port80software.com/products/zipenable/