Jboss and PostgresSQL Tuning for Muthoot ERP Environment: Difference between revisions
| Line 27: | Line 27: | ||
Check the difference between the created "post-pgtune.conf.sample" and Current "/var/lib/pgsql/data/postgresql.conf" | Check the difference between the created "post-pgtune.conf.sample" and Current "/var/lib/pgsql/data/postgresql.conf" | ||
diff post-pgtune.conf.sample /var/lib/pgsql/data/postgresql.conf | |||
diff post-pgtune.conf.sample /var/lib/pgsql/data/postgresql.conf | |||
The following lines were introduced in new configuration file | |||
#custom_variable_classes = '' # list of custom variable class names | |||
default_statistics_target = 50 # pgtune wizard 2013-07-25 | |||
maintenance_work_mem = 1GB # pgtune wizard 2013-07-25 | |||
constraint_exclusion = on # pgtune wizard 2013-07-25 | |||
checkpoint_completion_target = 0.9 # pgtune wizard 2013-07-25 | |||
effective_cache_size = 22GB # pgtune wizard 2013-07-25 | |||
work_mem = 192MB # pgtune wizard 2013-07-25 | |||
wal_buffers = 8MB # pgtune wizard 2013-07-25 | |||
checkpoint_segments = 16 # pgtune wizard 2013-07-25 | |||
shared_buffers = 7680MB # pgtune wizard 2013-07-25 | |||
max_connections = 80 # pgtune wizard 2013-07-25 | |||
As Muthoot Environment is on Redhat Cluster suite , check the cluster status via | As Muthoot Environment is on Redhat Cluster suite , check the cluster status via | ||
Revision as of 11:26, 12 August 2013
Objective : Tuning of Jboss (192.168.1.129) and PostgreSQl (Cluster- 192.168.1.140) for Muthoot Group
Issue : long Report from Application makes the JBOSS Server to hung and Finally we have restart the server . The Long report was not coming even after 1+ hours .
Approach :
- Tune postgreSql to use high available memory
- Tune JBOSS to use high available memory
PostgreSQL Tuning and Process
Install pgtune rpm package
yum install pgtune
Create a Sample configuration file based on current environment
pgtune -i /var/lib/pgsql/data/postgresql.conf -o post-pgtune.conf.sample
Check the difference between the created "post-pgtune.conf.sample" and Current "/var/lib/pgsql/data/postgresql.conf"
diff post-pgtune.conf.sample /var/lib/pgsql/data/postgresql.conf
The following lines were introduced in new configuration file
#custom_variable_classes = # list of custom variable class names default_statistics_target = 50 # pgtune wizard 2013-07-25 maintenance_work_mem = 1GB # pgtune wizard 2013-07-25 constraint_exclusion = on # pgtune wizard 2013-07-25 checkpoint_completion_target = 0.9 # pgtune wizard 2013-07-25 effective_cache_size = 22GB # pgtune wizard 2013-07-25 work_mem = 192MB # pgtune wizard 2013-07-25 wal_buffers = 8MB # pgtune wizard 2013-07-25 checkpoint_segments = 16 # pgtune wizard 2013-07-25 shared_buffers = 7680MB # pgtune wizard 2013-07-25 max_connections = 80 # pgtune wizard 2013-07-25
As Muthoot Environment is on Redhat Cluster suite , check the cluster status via
clustat
Stop the Cluster Services , which will bring down the postgresql too
clusvcadm -s Cluster-Service cd /var/lib/pgsql/data/ chown postgres.postgres post-pgtune.conf.sample cp -pvr postgresql.conf postgresql.conf.org_backedup_on_25_july_2013 cp -pvr post-pgtune.conf.sample postgresql.conf
Start the cluster so that PostgreSQL will start along
clusvcadm -R Cluster-Service
Test the environment
clustat ps -ef | grep postgre
JBOSS Tuning and Process
The Ram allocated to Jboss was less so needs to increase
Open the Jboss's run.conf file
vi /usr/bin/jboss-6.0.0.Final/bin/run.conf
Modify the old to new as shown below
# JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" JAVA_OPTS="-Xms12288m -Xmx12288m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
Test via
ps -ef | grep java