Re: Compression and SSL

[Pid]

On 02/11/2009 23:34, Jeffrey Janner wrote:
Pid -
Windows 64-bit Dual Quad-Core w/32G RAM.  Do I really need bigger?
App's not really slow-- works great here.  But with a 300ms latency
(one-way) to The Orient, you can see why I might want to send as few
bits as possible.
Jeff

Indeed. Was just asking.

What portion of the resources sent are static, and have you considered 
hosting those physically closer to your clients?

If you've got a typical web page type setup, then most of the response 
time is made up of the (bi)sequential download of the extra resources 
served after the browser has processed the HTML.

A quick look at the network profiler in Firebug ought to make it clear 
what's happening.

If you can expect an average of 250ms for *every* resource, then even 
the cost of a little big of logic, to set a different server URL for 
those static resources, will probably pay off big time.

Even a cheap low power server might offer a better service if the 
resources are small enough, and it's in the locality.


p




-----Original Message-----
From: Pid [mailto:p...@pidster.com]
Sent: Monday, November 02, 2009 12:12 PM
To: Tomcat Users List
Subject: Re: Compression and SSL

On 02/11/2009 16:48, Jeffrey Janner wrote:
OK, another newbie-ish question here.



I am using Tomcat 5.5.x with APR/native libraries on Windows 2003 x32
or
Windows 2008 x64 to serve applications from the US to Asia-based
clients.

We encrypt everything using SSL, from Login page onward, with
<transport-guarantee>   of CONFIDENTIAL.

All URLs are configured as relative, i.e., "/images/picture.png",
"/APP1?param1=value....", etc.

We use Tomcat as the web server with no intervening proxies,
load-balancers, accelerators, etc.

Response time is noticeably slow (based on complaint level) and I am
looking for ways to improve it.

Bigger server?

Will setting the HTTPS connector "compression=on" actually compress
the
data for HTTPS?

What makes you think that compressing things is going to improve
matters?  Doing the compression is an overhead itself.

What's slow about your app and how do you know it?


Does it compress before or after applying the encryption?

And,  in case it's relevant, here is the relevant excerpt from the
web.xml file we use:



    <security-constraint>

      <web-resource-collection>

        <web-resource-name>Everything</web-resource-name>

        <url-pattern>*.jsp</url-pattern>

        <url-pattern>*.html</url-pattern>

        <url-pattern>*.js</url-pattern>

Brevity:

    <url-pattern>/*</url-pattern>

        <url-pattern>/APP1</url-pattern>
        <url-pattern>/APP2</url-pattern>

If those actually represent real webapps, with their own
WEB-INF/web.xml, the lines above don't do anything.

p


      </web-resource-collection>

      <user-data-constraint>

        <transport-guarantee>CONFIDENTIAL</transport-guarantee>

      </user-data-constraint>

    </security-constraint>



Any assistance would be much appreciated.



Jeff


*******************************  NOTICE
*********************************
This message is intended for the use of the individual or entity to
which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law.  If the
reader of this message is not the intended recipient or the employee
or
agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution, or
copying
of this communication is strictly prohibited.  If you have received
this
communication in error, please notify us immediately by reply or by
telephone (call us collect at 512-343-9100) and immediately delete
this
message and all its attachments.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



*******************************  NOTICE  *********************************
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law.  If the
reader of this message is not the intended recipient or the employee or
agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this communication is strictly prohibited.  If you have received this
communication in error, please notify us immediately by reply or by
telephone (call us collect at 512-343-9100) and immediately delete this
message and all its attachments.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org