Matt, that is what I am trying to do. I can see that the size of the file
can be smaller, but I am looking at it from the client side. From the time I
hit the page, then it is displayed will it be quicker, longer or no
difference. I understand that time is needed to compress, uncompress and
transfer. I was hoping that there might be a tool out there that I can see
how long it takes to retrieve and view once received from the client side.
Regards
Andrew Scott
Technical Consultant
NuSphere Pty Ltd
Level 2/33 Bank Street
South Melbourne, Victoria, 3205
Phone: 03 9686 0485 - Fax: 03 9699 7976
_____
From: Matt Robertson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 14 January 2004 1:42 PM
To: CF-Talk
Subject: Re: Compression Filter
I think if you want to get serious about this the only way to do so is to
load test with compression on and off.
In my experience the performance penalty has never been noticeable even at
max compression (i.e. gzip compression via cf_gzippage set to max
compression). The bandwidth savings - especially on really large pages --
is enormous. You can measure how much directly by stopping that tag from
deleting its temp pages. Site maps with 200k of html reduced to 25k, for
example.
Same goes for IIS compression. No perceived speed difference or ill effects
that I have ever noticed.
Your mileage may vary. Especially under heavy load.
--
-------------------------------------------
Matt Robertson, [EMAIL PROTECTED]
MSB Designs, Inc. http://mysecretbase.com
-------------------------------------------
--
_____
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- Re: Compression Filter Matt Robertson
- RE: Compression Filter Andrew Scott
- RE: Compression Filter Matt Robertson
- Re: Compression Filter Jochem van Dieten
- RE: Compression Filter cf-talk
- RE: Compression Filter Andrew Scott
- RE: Compression Filter cf-talk
- RE: Compression Filter Andrew Scott
- Re: Compression Filter Thomas Chiverton