Yes, compression is enabled, at least on the real systems.
It was turned off in this local test.
However, turning on compression results in 43KB instead of 512 KB and
the response time is locally a little bit slower (17.5 sec).
So the problem with HTTPS is independent of the compression.
I just tried to measure the times with jetty without success.
Which jetty version do I have to use for myfaces 1.2?
I tried several ones (7.3.x, 7.2.x, 7.1.X) but I get always EL errors
with nested expressions which I do not get with Tomcat 6.0.X.
I never used Jetty so far, can I put Tomcat's EL impl into jetty?
Michael
Am 11.04.2011 15:28, schrieb Adrian Mitev:
Have you turned on the page compression of your app server?
2011/4/11 Walter Mourão<[email protected]>
As far as I know, the JSF does not know anything about https... it is
handled by the servlet container (Tomcat, Jetty...).
Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br
On Mon, Apr 11, 2011 at 8:49 AM, Michael Heinen<[email protected]
wrote:
Hi,
My JSF application is very slow via HTTPS.
Some parts are 15 times slower compared to HTTP
I measured the response times of the xhtml requests with Fiddler (locally
and over network)
Result for a very large page (512 KB) with a big datatable without ajax
usage:
-- local access with HTTP: 1 sec
-- local access with HTTPS: 15-16 sec
Other pages are factor 2-4 slower, with or without ajax.
The time is spent in htmlTableRenderer.encodeInnerHtml. Data is of course
available, there is no additional backend access.
The simple download of xhtml files or other files is NOT (noticeable)
slower.
Other non JSF applications running on the same servers are also not
slower
with HTTPS.
Before I start profiling:
- Does anybody have an idea where I should look at?
- Are there any known JSF or webApp settings that influence https
performance?
Environment:
Facelets
myFaces 1.2.9
tomahawk12_1.1.10
richfaces 3.3.3
tomcat 6.0.29
jdk 1.6.0_23
Regards,
Michael
