About the setting "Http Compression" of IIS. Is is really useful for web application?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Benny Ng - 29 Nov 2006 06:40 GMT

Dear All,

Now I met some performance problems in my application. Because according
to our business. The size of some web forms are larger than 1xxx MB. So it
takes a long time for user opening a web page. Surely we are modifying some
source code for performance improvment.

But now i'm thinking should we improve the application performance by
IIS Compression? I saw many mentions from Google/Yahoo. Some people said it
can be useful for performance improvment. But some peoples strongly
suggested NOT to enabled this option in IIS. Because it would let the system
and application not stable. Or sometimes the application can't get the
newest data from server.

I don't know more about the IIS Compression. So Is anyone know this
option and already used it? Any suggestion for this Option?

Because if this option would let the application not stabled. Then I
prefer NOT to enable this option. Because DATA is more important than SPEED.

Any suggestions from you are appreciated. Thanks,

Best Regards,

Benny Ng

Reply to this Message

Laurent Bugnion - 29 Nov 2006 09:26 GMT

Hi,

> Dear All,
>
[quoted text clipped - 21 lines]
>
> Benny Ng

Are you related to my wife? (Ng Chi Meei) (just kidding, Ng must be the
most widespread cantonese last name if I am not mistaken ;-)

Anyway...

Compression is a way to move the performance problem from one place to
the other. if you don't compress, you transmit more data on the network,
which may cause performance problems. On the other hand, if you
compress, you transmit less data, but the server and the client have
more load (they must compress and uncompress the data).

So the answer is: It depends (it's often the answer when you do
engineering). If your typical user has a modem connection and a good PC,
and if your server is powerful enough, compression can be a real help,
especially if you have a lot of text data (ASPX, JavaScript, CSS,
etc...) (compression for images won't help much, as JPGs, GIFs or PNGs
used on the web are mostly very compressed already).

OTOH, if your users have ADSL, I am not sure it's worth bothering with
compression.

I am not aware of stability problems when using compression. We use it
in one of our projects without problems. However, it's a good idea to
make it optional for the users.

HTH,
Laurent

Signature

Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
Private/Malaysia: http://mypage.bluewin.ch/lbugnion
Support children in Calcutta: http://www.calcutta-espoir.ch

Reply to this Message

Benny Ng - 30 Nov 2006 07:51 GMT

Dear Laurent,

Haha,Yes. "Ng" is a wildspread Last Name in China. I think it's top 20
Last Name. :)

For the environment of our company. We are using two ADSL+DDN connect to
Canada,HongKong and China.

I don't think the network is too slowly for us.

All of our application are using the ASPX. There is no many image files
on our application. Because I'm afraid it would be not stabled if we enabled
this option.

Because in before we got some experience for this option. It would let
the application can not get the new data. (But only for some time/some
cases)

So that's my concern for that.

But anyway, Thank you very much.

By the way, If you don't mind, You can add my MSN account. We can talk
about the technical or another thing on it. haha..Thanks.

my MSN: benny_wufree@hotmail.com

Best Regards,

Benny Ng

> Hi,
>
[quoted text clipped - 52 lines]
> HTH,
> Laurent

Reply to this Message

Rate this thread:

About the setting "Http Compression" of IIS. Is is really useful for web application?

Free Magazines