[MAGNOLIA-7754] Magnolia + wildfly + java 11 leads to performance issue Created: 23/Mar/20  Updated: 23/Mar/20

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: 5.7.6, 6.1.4
Fix Version/s: None

Type: Task Priority: High
Reporter: Aymeric Levaux Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AKS


Issue Links:
Cloners
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

When we upgraded to java 11 (from java 8), there was noticed a significant performance decrease on Magnolia.

After investigating, it appears we are running into the issue as reported here: https://issues.redhat.com/projects/LOGMGR/issues/LOGMGR-263. A lot of threads are getting slowed down because of a call to MethodUtils.getMatchingAccessibleMethod(...) from "commons-beanutils" which is called indirectly by Magnolia from "info.magnolia.rendering.renderer.AbstractRenderer.newModel(Class, Node, RenderableDefinition, RenderingModel) AbstractRenderer.java:258" (BeanUtils.populate(...) call). The MethodUtils.getMatchingAccessibleMethod creates a new Logger on each call resulting in the issue described in the redhat issue.

After implementing the workaround suggested here https://issues.redhat.com/browse/LOGMGR-263?focusedCommentId=13975980&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13975980 as a test, the performance returned back to what we had with java 8.

Tested with Wildfly 13 and Wildfly 18.


Generated at Mon Feb 12 04:26:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.