I have installed the HttpCompression from blowery.org and followed the stepsin the following page.
http://www.dnncreative.com/Tutorial...fault.aspx

After this I had to remove the ICSharpCode.SharpZipLib.xml and ICSharpCode.SharpZipLib.dll files as they were giving compliation error.

Ok, Now how can i see the module or its setting to modify or enable other features if it has?
How can i know if there is a performacne increase, as i can see no changes in the performace state.

thank you.

Assuming that you are using a current version of DotNetNuke, the HttpCompression tools are built in. So, I would recommend that you put those libraries back and remove the blowery.org code.

The recommended settings for performance (courtesy of John Mitchell at snapsis.com) are:

"If you are not using PageBlaster then I would recommend setting the performance settings as follows:

Page State Persistence: Page
You could try memory, but I believe there are too many problems here without much gain especially as a global setting.

Module Caching Method: Memory
Memory is much faster, and there are intermittent errors when using Disk.

Performance Setting: Heavy
There is really not much difference between the different settings here. The setting is just a multiplier that gives you only 5 hours of caching at the most (depending on the object) when on Heavy. Some items are not cached at all unless you are on Heavy.

Authenticated Cacheability: Set it to public.
This allows the client browser or downstream proxies to cache items.

Compression Setting: Deflate or Gzip does not matter.
They are both about the same and will vary depending on content. I use Gzip.

Compression Level: There is a bug that is keeping it from being applied, but it should be around five, higher than that gives diminishing return.

Use Whitespace Filter: Not Checked
Don't use it if you have compression on it is a waste of time, because compression also removes white space.

If you are using PageBlaster then you should replace the core compression module in the HttpModules section of Web.config.
All the settings above should remain the same, because PageBlaster does not cache authenticated user requests by default."