Ethernet uses packets of 1500 bytes, this includes some headers. So if your
html is smaller than about 1400 bytes your are sending the same number of
packets over your network with or without compression. If the size of the html
is larger you are winning some packets/sec with compression. But I can't say
this saves you some cpu time for not compressing small pages. If the
performance of your application depends on these small things you have a very
efficient application. ;-) I think you can better spend some time profiling the
rest of the application to win in cpu speed.
NB: The ethernet packet size isn't the 'global internet' packet size, but most
networks support this size.
Compressing images is useless. We compress css and javascript and don't have
problems with it, but our customers use quite new browsers, because the
application doesn't work in pre-mozilla/pre-ie-5.5 at all.
Ronald.
On Fri Jul 29 04:20:35 CEST 2005 Tomcat Users List
<[email protected]> wrote:
thanx for ur help
i will go forward in using GZIP for my application.
can you tell me what would be the ideal page (or image or what ever it
may be) size over which we can apply compression, so that we dont
waste resources compressing smaller pages. I think may be compressing
each and every page will negate the gains that we achieve by
compressing.
Also can you tell me whether it is appropriate to apply compression on
image files (like .gif, . jpeg etc) as some of image formats are
compressed already in themselves.
Regards
Srikanth
On 7/26/05, Ronald Klop <[EMAIL PROTECTED]> wrote:
> If you have enough bandwidth yourself, the big win is in the saved bandwidth
on the client-side and that is what your customers like. The browser wil act
quicker because it has more data to render in a shorter time.
>
> On Tue Jul 26 12:46:07 CEST 2005 Tomcat Users List <[email protected]> wrote:
> > It will eat up CPU, but you also save CPU by not having to transmit those
> > extra bytes.
> >
> > Its always a good idea to GZIP.
> >
> > -Tim
> >
> > Peddireddy Srikanth wrote:
> >
> > > Hi all,
> > > Iam planning to turn on the HTTP/1.1 GZIP compression for my
> > > application by setting the compression attribute of http connector.
> > > Iam sure that this will reduce my bandwidth requirements.
> > > But I have a doubt. Is Compressing the responses will eat away many
> > > CPU cycles and affect my throughput or performance or scalability.
> > >
> > > Any one have used this option in production environment and what r the
> > > results(performance etc)
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
