Performance Tuning With Liferay

Introduction

Performance tuning is a critical aspect of maintaining and optimizing any applications to ensure they meet the demands of users while efficiently utilizing system resources. Liferay is a powerful platform for building enterprise portals and digital experiences, but as with any complex software system, ensuring optimal performance requires careful planning, monitoring, and optimization.

The performance of the portal is mainly divided into two sections.

Front end performance
Backend performance

To optimize the performance of the portal we need to perform various steps mentioned below

Front-end performance tuning

Images	Use Standard size images on the webpage. Compress the image size according to the PX ratio. Use the proper format of the image (WebP). Use adaptive media images for mobile and other devices.
Java Script	Enable Lazy loading. Minify the JS. Use the CDN for JS loading.
Templates	Minimize the front-end manipulation.
Content compression	Install the content compression tool at the web server level

Back-end performance tuning

AJP connector	Use AJP connection between Web server to app server calls Also, you can apply tuning using the below attributes <Connector port=”8009″ protocol=”AJP/1.3″ redirectPort=”8443″ maxThreads=”450″ connectionTimeout=”20000″ keepAliveTimeout=”10000″ URIEncoding=”UTF-8″ />
Database configurations	We can update these properties for database tuning in Liferay jdbc.default.connectionTimeout=30000 jdbc.default.idleTimeout=600000 jdbc.default.maximumPoolSize=100 jdbc.default.maxLifetime=0 jdbc.default.minimumIdle=10 jdbc.default.registerMbeans=true
Cloudflare	Use Cloudflare for better caching
Portal properties configurations	Disable unused filters from liferay 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 com.liferay.portal.servlet.filters.gzip.GZipFilter=false com.liferay.portal.servlet.filters.strip.StripFilter=false com.liferay.portal.sharepoint.SharepointFilter=false com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter=true com.liferay.portal.servlet.filters.validhtml.ValidHtmlFilter=false Add the below properties for better performance. direct.servlet.context.reload=false session.tracker.memory.enabled=false counter.increment=2000 dl.file.rank.enabled=false dl.file.entry.read.count.enabled=false permissions.inline.sql.check.enabled=false Disable the Developer mode from liferay The property’s name depends on the Liferay version.

AJP connector

Use AJP connection between Web server to app server calls
Also, you can apply tuning using the below attributes

<Connector port=”8009″ protocol=”AJP/1.3″

redirectPort=”8443″

maxThreads=”450″

connectionTimeout=”20000″

keepAliveTimeout=”10000″

URIEncoding=”UTF-8″ />

Database configurations

We can update these properties for database tuning in Liferay

jdbc.default.connectionTimeout=30000

jdbc.default.idleTimeout=600000

jdbc.default.maximumPoolSize=100

jdbc.default.maxLifetime=0

jdbc.default.minimumIdle=10

jdbc.default.registerMbeans=true

Cloudflare

Use Cloudflare for better caching

Portal properties configurations

Disable unused filters from liferay

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

com.liferay.portal.servlet.filters.gzip.GZipFilter=false

com.liferay.portal.servlet.filters.strip.StripFilter=false

com.liferay.portal.sharepoint.SharepointFilter=false

com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter=true

com.liferay.portal.servlet.filters.validhtml.ValidHtmlFilter=false

Add the below properties for better performance.

direct.servlet.context.reload=false

session.tracker.memory.enabled=false

counter.increment=2000

dl.file.rank.enabled=false

dl.file.entry.read.count.enabled=false

permissions.inline.sql.check.enabled=false

Disable the Developer mode from liferay
The property’s name depends on the Liferay version.

Performance tuning: Verification

Jmeter	Performs a backend load test Can check the timing of each request, failure counts, etc.
Lighthouse	Performs a front-end performance test Provides front-end performance tuning guidelines

Conclusion

In conclusion, optimizing Liferay’s performance involves a multifaceted approach that includes tuning various components such as the application server, database, caching mechanisms, and the Liferay configuration itself.