Version Differences for Performance Tuning Servers

Revision as of 01 May 2012 17:30 n

(Initial post of JVM Performance Options)

Revision as of 02 May 2012 11:48

(Add base.xml info)

 The default settings for the AnthillPro server tend to work well for many customers.  However, in extreme cases where either the server hardware has limitations, or the server activity and user base is large, these tuning options may help.
-                '''JVM (Oracle) Options'''
+                <br>'''JVM (Oracle) Options'''
 Adding these options to the setenv.sh file (3.8.3+), or modifying your ah3server launch script to include these arguments will improve the server's usage of available resources and UI responsiveness.
 * -Xss### | ''Sets the maximum thread stack size to "###".  For most systems this should be set the same as the initial stack size at 128k (32 bit) or 256k (64 bit).  DO NOT FORGET SIZE DESCRIPTOR (k, m, g).''
-                '''JVM (IBM) Options'''
+                <br>'''JVM (IBM) Options'''
 Adding these options to the setenv.sh file (3.8.3+), or modifying your ah3server launch script to include these arguments will improve the server's usage of available resources and UI responsiveness.
 * -Xiss### | ''Sets the initial thread stack size to "###".  For most systems this should be set the same as the maximum stack size at 128k (32 bit) or 256k (64 bit).  DO NOT FORGET SIZE DESCRIPTOR (k, m, g).''
 * -Xss### | ''Sets the maximum thread stack size to "###".  For most systems this should be set the same as the initial stack size at 128k (32 bit) or 256k (64 bit).  DO NOT FORGET SIZE DESCRIPTOR (k, m, g).''
                 <br>'''Database Connections (base.xml)'''
                 The following additions and modifications can increase the amount of database connections used by AnthillPro and improve UI responsiveness for systems with a large user base.
                 ''Modify:''
                 <pre>  <bean id="dataSource0" class="com.urbancode.anthill3.spring.DecryptPasswordDataSource"
                         destroy-method="close">
                     <property name="driverClassName">
                       <value>${install.db.driver}</value>
                     </property>
                     <property name="url">
                       <value>${install.db.url}</value>
                     </property>
                     <property name="username">
                       <value>${install.db.user}</value>
                     </property>
                     <property name="password">
                       <value>${install.db.password}</value>
                     </property>
                     <property name="maxActive">
                      <value>280</value>
                     </property>
                     <property name="maxIdle">
                      <value>280</value>
                     </property>
                     <property name="minIdle">
                      <value>280</value>
                     </property>
                     <property name="defaultTransactionIsolation">
                       <value>2</value>
                     </property>
                     <property name="testOnBorrow">
                       <value>true</value>
                     </property>
                     <property name="validationQuery">
                       <value>${install.db.validationQuery}</value>
                     </property>
                     <!-- not available in our version or the database connection pool library
                     <property name="validationQueryTimeout">
                       <value>10</value>
                     </property>
                     -->
                     <!-- track abandoned connections. this adds a overhead. only enable if connections are being leaked.
                     <property name="logAbandoned">
                       <value>true</value>
                     </property>
                     <property name="removeAbandonedTimeout">
                       <value>300</value>
                     </property>
                     <property name="removeAbandoned">
                       <value>false</value>
                     </property>
                      -->
                   </bean>
                 </pre>
                 ''Add:''
                 <pre>  <bean id="dataSource1" class="com.urbancode.anthill3.spring.DecryptPasswordDataSource"
                         destroy-method="close">
                     <property name="driverClassName">
                       <value>${install.db.driver}</value>
                     </property>
                     <property name="url">
                       <value>${install.db.url}</value>
                     </property>
                     <property name="username">
                       <value>${install.db.user}</value>
                     </property>
                     <property name="password">
                       <value>${install.db.password}</value>
                     </property>
                     <property name="maxActive">
                      <value>20</value>
                     </property>
                     <property name="maxIdle">
                      <value>20</value>
                     </property>
                     <property name="minIdle">
                      <value>20</value>
                     </property>
                     <property name="defaultTransactionIsolation">
                       <value>2</value>
                     </property>
                     <property name="testOnBorrow">
                       <value>true</value>
                     </property>
                     <property name="validationQuery">
                       <value>${install.db.validationQuery}</value>
                     </property>
                     <!-- not available in our version or the database connection pool library
                     <property name="validationQueryTimeout">
                       <value>10</value>
                     </property>
                     -->
                     <!-- track abandoned connections. this adds a overhead. only enable if connections are being leaked.
                     <property name="logAbandoned">
                       <value>true</value>
                     </property>
                     <property name="removeAbandonedTimeout">
                       <value>300</value>
                     </property>
                     <property name="removeAbandoned">
                       <value>false</value>
                     </property>
                      -->
                   </bean></pre>
                 ''Modify:''
                 <pre>  <!-- DataSource used for identity generation so it does not create deadlocks -->
                   <bean id="identityDataSource" class="com.p6spy.engine.spy.P6DataSource" destroy-method="close" scope="singleton">
                     <constructor-arg>
                       <ref local="dataSource1"/>
                     </constructor-arg>
                   </bean></pre>