Mime Compression in the server.xml file
Hi,
Following a series of performance and network issues, our IT administrator has recommended to apply compression in the Tomcat configuration file.
That is, to add the following line in the server.xml file -
<Connector URIEncoding="UTF-8" acceptCount="100" connectionTimeout="20000"
disableUploadTimeout="true" enableLookups="false"
maxHttpHeaderSize="8192" maxSpareThreads="75"
maxThreads="500" minSpareThreads="25" port="9089"
redirectPort="9080" compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml, text/javascript,text/css,application/javascript" />
By doing this change, will it impact the system in anyway and are there any case studies that this has improved the performance/network problems?
|
Accepted answer
Hi Sunita,
Maybye it is not direct answer on your question but might help you. See https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=113717 comment 2 which indicates that default settings are fine. Also according to https://jazz.net/forum/questions/75418/when-data-compression-happens-client-or-server scm data is compressed as default. Let us know if it helps. Sunita Dinakar selected this answer as the correct answer
|
One other answer
Hi Krzysztof, On the Jazz admin page, the compressed setting seemed to be ON. However, on the Tomcat server.xml, the compression parameters are commented. Are these compression parameters in the server.xml for a different purpose then ?
Comments
Krzysztof Kaźmierczyk
commented Oct 10 '13, 8:13 a.m.
Hi Pavithra,
Pavithra Kasturirangan
commented Oct 10 '13, 8:14 a.m.
So in your opinion, is it recommended to set the compression in Tomcat as well ? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.