What the heck are you talking about "No it doesn't"? LOL
All I said was that you can use the "demo" page from other companies to
test and see how much data your sending in regular mode vs compressed
mode.
Yes, you should have been more descriptive. I didn't realize that what
you're REALLY trying to find out is what the overhead is on compression
(ie. how much time does it take to compress/decompress the page)
The answer to that question varies (of course) on the speed of your
server and the speed of the client's computer. It's kinda like asking
"How fast is _javascript_?" (depends on the speed of the client's
computer)
I can't tell you anything scientific about viewing times for compressed
pages but I can tell you that it does save A LOT of bandwidth. If you
have you're own T1 and it's nowhere near saturation then this probably
doesn't mean much to you. If you're at a colocation and paying for
bandwidth... then it certainly does matter. :)
I've installed compression on several of our production servers... web
applications that typically spit out 30-40k pages of database text. The
perceived page view time isn't really noticable (if at all). We tested
it with a basic run-of-the-mill computer... 800Mhz, 1Ghz machines...
I've never tried it on something like a Pentium 200Mhz or anything like
that.
-Novak
-----Original Message-----
From: Andrew Scott [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 2:41 PM
To: CF-Talk
Subject: RE: Compression Filter
Novak,
Actually no it doesn't!
I am aware of how compression works, I am aware that it can send the
file
quicker with less bandwidth.
What I am not aware, and maybe I should have been a little more
descriptive.
When Coldfusion executes the cfml template, then sends and the client
receives this. In that scenario the factor is the time the page takes to
execute, the time it takes to for the client to see the final page. Now
if I
switch compression on from the server via a filter or ISAPI, what extra
time
does this take on the server to compress the file and what extra time
does
it take for the client to view the file. This is what I want to know, we
have small files about 30k-60k in size that do compress down to about
5-10k,
but I need to measure if saving the bandwidth is an actual saving in
viewing
time overall.
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 15 January 2004 4:27 AM
To: CF-Talk
Subject: RE: Compression Filter
Andrew,
Perhaps not the best answer but when I put compression in place on our
servers the way I compared was by visiting websites of companies that
sell compression software and used their "demo" page. You probably know
the type I'm talking about... you put in a URL... they fetch it and then
tell you if it can be compressed or not and if it can be compressed by
how much, etc.
If you pass an already compressed page it will tell you the page can't
be compressed further and give you the file size, etc. Some will also
tell you the uncompressed file size.
Hope this helps,
-Novak
-----Original Message-----
From: Andrew Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 6:49 PM
To: CF-Talk
Subject: RE: Compression Filter
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]
