Here is some bench marks which can increase your system performance :
Please see below details which can be taken care for Liferay performance benchmark.
1) First step to increase performance is hardware configuration.
So Hardware Configuration as per Liferay 6.1 EE Performance Whitepaper
•Web Server (Apache Web Server)
•1 x Intel Core 2 Duo E6405 2.13GHz CPU, 2MB L2 cache (2 cores total)
•4GB memory
•1 x 146GB 7.2k RPM IDE
•Application Server (Liferay Portal Server)
•2 x Intel Core 2 Quad X5677 3.46GHz CPU, 12MB L2 cache (8 cores and 16 threads)
•16GB memory
•2 x 146GB 10k RPM SCSI
•Database Server
•2 x Intel Core 2 Quad X5677 3.46GHz CPU, 12MB L2 cache (8 cores and 16 threads)
•16GB memory
•4 x 146GB 15k RPM SCSI
2) How to scale web server and application server ?
Need to arrange web server according to load of the system.Also It is recommended to use multiple database instances with cluster environment with proper load balancer configurations.
3) Recommended JVM Configuration
Initial JVM Configuration for Liferay Portal server 32bit JVM:
–-server -XX:NewSize=700m -XX:MaxNewSize=700m -Xms2048m -Xmx2048m -XX:MaxPermSize=200m -XX:SurvivorRatio=6 –XX:TargetSurvivorRatio=90 –XX:MaxTenuringThreshold=15
Initial JVM Configuration for Liferay Portal server 64bit JVM :
–-server -d64 -XX:NewSize=3072m -XX:MaxNewSize=3072m -Xms6144m -Xmx6144m -XX:PermSize=200m -XX:MaxPermSize=200m -XX:SurvivorRatio=90 -XX:TargetSurvivorRatio=0 -XX:MaxTenuringThreshold=0 -XX:+UseParNewGC -XX:ParallelGCThreads=16 -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSCompactWhenClearAllSoftRefs -XX:CMSInitiatingOccupancyFraction=85 -XX:+CMSScavengeBeforeRemark -XX:+CMSConcurrentMTEnabled -XX:ParallelCMSThreads=2-XX:+UseLargePages -XX:LargePageSizeInBytes=256m -XX:+UseCompressedOops -XX:+DisableExplicitGC -XX:-UseBiasedLocking -XX:+BindGCTaskThreadsToCPUs -XX:+UseFastAccessorMethods
4) Remove unnecessary servlet filters using portal-ext.properties:
like...
com.liferay.portal.servlet.filters.sso.cas.CASFilter=false
com.liferay.portal.servlet.filters.sso.ntlm.NtlmFilter=false
com.liferay.portal.servlet.filters.sso.ntlm.NtlmPostFilter=false
com.liferay.portal.servlet.filters.sso.opensso.OpenSSOFilter=false
etc..
You can find other filters in portal.properties from portal source code and make t disable
5)Disable portlet CSS & Look and feel by using below property which will helo to increase perfomance by reducing CSS load for each portlet (Not mandatory and it depends on requirement)
–portlet.css.enabled=false
–look.and.feel.modifiable=false
6) Disable user's public and private layout if not require (I think we already applied in properties)
–layout.user.private.layouts.enabled=false
–layout.user.public.layouts.enabled=false
7) Disable Direct Servlet context reload
Liferay has a feature to dispatch taglib jsps directly through servlet
•This feature improves performances and is by default enabled
•But this feature always checks corresponding JSP of a particular type for any change
•For production environment, it is not required to check Tag JSP file
•To disable this option we need to add following line in portal-ext.properties
–direct.servlet.context.reload=false
8) Disable pingbacks and trackbacks
Liferay’s collaboration features like blogging and message boards provide Pingbacks and Trackbacks support
•These features increases network traffic
•These features are enabled by default
•It such features are not used then it is a best practice to disable them by adding following properties
–blogs.pingback.enabled=false
–blogs.trackback.enabled=false
–blogs.ping.google.enabled=false
–message.boards.pingback.enabled=false
9) You can refer below links from liferay.com which can help for other performance tuning steps
http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/performance-tuni-5
http://www.liferay.com/community/wiki/-/wiki/Main/Performance
Please see below details which can be taken care for Liferay performance benchmark.
1) First step to increase performance is hardware configuration.
So Hardware Configuration as per Liferay 6.1 EE Performance Whitepaper
•Web Server (Apache Web Server)
•1 x Intel Core 2 Duo E6405 2.13GHz CPU, 2MB L2 cache (2 cores total)
•4GB memory
•1 x 146GB 7.2k RPM IDE
•Application Server (Liferay Portal Server)
•2 x Intel Core 2 Quad X5677 3.46GHz CPU, 12MB L2 cache (8 cores and 16 threads)
•16GB memory
•2 x 146GB 10k RPM SCSI
•Database Server
•2 x Intel Core 2 Quad X5677 3.46GHz CPU, 12MB L2 cache (8 cores and 16 threads)
•16GB memory
•4 x 146GB 15k RPM SCSI
2) How to scale web server and application server ?
Need to arrange web server according to load of the system.Also It is recommended to use multiple database instances with cluster environment with proper load balancer configurations.
3) Recommended JVM Configuration
Initial JVM Configuration for Liferay Portal server 32bit JVM:
–-server -XX:NewSize=700m -XX:MaxNewSize=700m -Xms2048m -Xmx2048m -XX:MaxPermSize=200m -XX:SurvivorRatio=6 –XX:TargetSurvivorRatio=90 –XX:MaxTenuringThreshold=15
Initial JVM Configuration for Liferay Portal server 64bit JVM :
–-server -d64 -XX:NewSize=3072m -XX:MaxNewSize=3072m -Xms6144m -Xmx6144m -XX:PermSize=200m -XX:MaxPermSize=200m -XX:SurvivorRatio=90 -XX:TargetSurvivorRatio=0 -XX:MaxTenuringThreshold=0 -XX:+UseParNewGC -XX:ParallelGCThreads=16 -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSCompactWhenClearAllSoftRefs -XX:CMSInitiatingOccupancyFraction=85 -XX:+CMSScavengeBeforeRemark -XX:+CMSConcurrentMTEnabled -XX:ParallelCMSThreads=2-XX:+UseLargePages -XX:LargePageSizeInBytes=256m -XX:+UseCompressedOops -XX:+DisableExplicitGC -XX:-UseBiasedLocking -XX:+BindGCTaskThreadsToCPUs -XX:+UseFastAccessorMethods
4) Remove unnecessary servlet filters using portal-ext.properties:
like...
com.liferay.portal.servlet.filters.sso.cas.CASFilter=false
com.liferay.portal.servlet.filters.sso.ntlm.NtlmFilter=false
com.liferay.portal.servlet.filters.sso.ntlm.NtlmPostFilter=false
com.liferay.portal.servlet.filters.sso.opensso.OpenSSOFilter=false
etc..
You can find other filters in portal.properties from portal source code and make t disable
5)Disable portlet CSS & Look and feel by using below property which will helo to increase perfomance by reducing CSS load for each portlet (Not mandatory and it depends on requirement)
–portlet.css.enabled=false
–look.and.feel.modifiable=false
6) Disable user's public and private layout if not require (I think we already applied in properties)
–layout.user.private.layouts.enabled=false
–layout.user.public.layouts.enabled=false
7) Disable Direct Servlet context reload
Liferay has a feature to dispatch taglib jsps directly through servlet
•This feature improves performances and is by default enabled
•But this feature always checks corresponding JSP of a particular type for any change
•For production environment, it is not required to check Tag JSP file
•To disable this option we need to add following line in portal-ext.properties
–direct.servlet.context.reload=false
8) Disable pingbacks and trackbacks
Liferay’s collaboration features like blogging and message boards provide Pingbacks and Trackbacks support
•These features increases network traffic
•These features are enabled by default
•It such features are not used then it is a best practice to disable them by adding following properties
–blogs.pingback.enabled=false
–blogs.trackback.enabled=false
–blogs.ping.google.enabled=false
–message.boards.pingback.enabled=false
9) You can refer below links from liferay.com which can help for other performance tuning steps
http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/performance-tuni-5
http://www.liferay.com/community/wiki/-/wiki/Main/Performance
Posts
