cancel
Showing results for 
Search instead for 
Did you mean: 

Tomcat gzip configuration not working - Community 5.1g

g_rathod
Star Contributor
Star Contributor

Team, 

Recently I want to have vanilla test with siteminder and installed  version 5.1g community edition

I configured my SSO and it is working, but I observed that it is taking too much time to load dashboard.

From Siteminder login page to Alfresco dashboard page it took more than 2 min.

Before gzip applied

Before gzip applied

After gzip applied

After gzip applied

I am surprised looking at result,

After compression it is taking 2.5 minutes to load dashboard and without compression it took 2min.

One thing I am not able to figure out, even we refresh alfresco dashboard,why it is downloading every resources from scratch? I can see there are 89 requests and around 3.4 mb transffered.

Here is my compression setting in server.xml

<Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1"
connectionTimeout="20000"
compression="on"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml,text/css, application/xml, application/xhtml+xml, application/rss+xml, application/javascript, application/x-javascript"
redirectPort="8443" maxHttpHeaderSize="32768" />

Is there any way to load dashboard page faster?  2 minute to load dashboard is very disappointed.

Thanks,

Ghanshyam

1 ACCEPTED ANSWER

afaust
Legendary Innovator
Legendary Innovator

First of all, compression and caching should always be handled by a front-end web server / proxy. Second of all, make sure you have configured Share to use the flag client-debug with false as the value (share-config-custom.xml) so that Share/Surf actually cache generated Aikau resources. Third of all, it is advisable to create a post-startup script that loads Aikau enabled pages so the resources are generated in advance of the first user access.

View answer in original post

2 REPLIES 2

afaust
Legendary Innovator
Legendary Innovator

First of all, compression and caching should always be handled by a front-end web server / proxy. Second of all, make sure you have configured Share to use the flag client-debug with false as the value (share-config-custom.xml) so that Share/Surf actually cache generated Aikau resources. Third of all, it is advisable to create a post-startup script that loads Aikau enabled pages so the resources are generated in advance of the first user access.

g_rathod
Star Contributor
Star Contributor

Thanks Axel for reply,

I am actually looking at options if anything that can be done via app server (tomcat). as we do not have any cluster or anything, this is simplest setup having solr integrated with same alfresco node.