This document provides steps to tune the Hybris platform for optimal performance. It recommends enabling JMX remote monitoring, tuning JVM memory and GC parameters based on load testing, modifying thread pool parameters, improving caching, analyzing thread dumps, and enabling JDBC logging to identify slow database queries. Performance tuning is an iterative process that involves applying load, monitoring resources, and adjusting configuration values.
This document provides steps to tune the Hybris platform for optimal performance. It recommends enabling JMX remote monitoring, tuning JVM memory and GC parameters based on load testing, modifying thread pool parameters, improving caching, analyzing thread dumps, and enabling JDBC logging to identify slow database queries. Performance tuning is an iterative process that involves applying load, monitoring resources, and adjusting configuration values.
This document provides steps to tune the Hybris platform for optimal performance. It recommends enabling JMX remote monitoring, tuning JVM memory and GC parameters based on load testing, modifying thread pool parameters, improving caching, analyzing thread dumps, and enabling JDBC logging to identify slow database queries. Performance tuning is an iterative process that involves applying load, monitoring resources, and adjusting configuration values.
This document provides steps to tune the Hybris platform for optimal performance. It recommends enabling JMX remote monitoring, tuning JVM memory and GC parameters based on load testing, modifying thread pool parameters, improving caching, analyzing thread dumps, and enabling JDBC logging to identify slow database queries. Performance tuning is an iterative process that involves applying load, monitoring resources, and adjusting configuration values.
Albin Issac www.albinsblog.com This document explains the approach to tune the Hybris platform.
Enable JMX Remote monitoring:
Remote JMX monitoring will help us to monitor the server resources (e.g. memory usage and CPU usage) through JMX client such as VisualVM.
Open <<HYBRIS_HOME>>/conf/local.properties and make sure the following properties are
added as part of tomcat.generaloptions .
-Dcom.sun.management.jmxremote.port=50055 - Dcom.sun.management.jmxremote.authenticate=false - Dcom.sun.management.jmxremote.ssl=false - Memory usage also can be monitored from admin console
Monitoring Memory
JVM Tuning:
The default JVM parameters are not optimal for running large applications. So the parameters (e.g. memory and GC) should be tuned for optimal performance of the application.
Create a folder crash under <<HYBRIS_HOME>>
Open <<HYBRIS_HOME>>/conf/local.properties and replace the variable java.mem with
the java.mem=6G Open <<HYBRIS_HOME>>/conf/local.properties replace tomcat.generaloptions with the following data
Change the XX:HeapDumpPath and –Xloggc path accordingly
Apply the required load to the system – Apache JMeter can be used to load the request to the system. Monitor the system resources like CPU, Memory and threads using VisualVM while load is applied to the system Change the memory parameters and GC parameters based on the above test result.
If you provide too little memory to an application it will run out of memory. The JVM will not be able to free up memory space at the rate that your application needs it. In this scenario JVM will throw an OutOfMemoryError and shut down completely
The above three steps should be repeated to achieve the optimum system performance by applying different values for the parameters. Thread Tuning:
Modify the thread parameters based on the system performance.
Open <<HYBRIS_HOME>>/bin/platform/ project.properties and replace the following
property values.
tomcat.acceptcount=150
tomcat.maxthreads=300
Change the counts accordingly.
Open <<HYBRIS_HOME>>/ config/tomcat/conf/server.xml
Open <<HYBRIS_HOME>>/ bin/platform/project.properties
Replace cache.main property value with cache.main=50000
Thread Dumps:
Thread Dump is a snapshot taken at a given time which provides with a complete listing of all created Java Threads. The thread dump can be analyzed to determine the bottleneck or blocking threads.
Different tools can be used to analyze the thread dumps e.g. Samurai and IBM Thread and Monitor Dump Analyzer for Java.
Thread Dump can be generated from admin console
Monitoring Thread Dump
Click on Download button to download the current thread dump.
JDBC Logging:
Sometimes the application will be very slow due to slow running queries. Analyzing the slower running queries using JDBC logging and create the indexes wherever required can drastically improve performance.
Monitoring Database JDBC logging
Click on Start logging and click on Stop logging after particular time.
Click on Download log
Click on JDBC log analysis Analyze to find out the details on the queries executed.
