[ https://issues.apache.org/jira/browse/SLING-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-4866. --------------------------------- Resolution: Cannot Reproduce I figured out that this is not an issue of the JSP scripting engine. The tests in question were initially run on a Sling Launchpad 7 instance, to which the Sightly bundles were installed through the maven-launchpad-plugin. The performance degradation was discovered after switching to the provisioning model for the tests, which required Sling Launchpad 8-SNAPSHOT. > JSP scripting engine performance degraded in org.apache.sling.scripting.jsp > 2.1.6 > --------------------------------------------------------------------------------- > > Key: SLING-4866 > URL: https://issues.apache.org/jira/browse/SLING-4866 > Project: Sling > Issue Type: Bug > Components: Scripting > Affects Versions: Scripting JSP 2.1.6 > Reporter: Radu Cotescu > Priority: Critical > Fix For: Scripting JSP 2.1.8 > > > The commit applied in > [r1629144|https://svn.apache.org/viewvc?view=revision&revision=1629144] seems > to have affected the JSP scripting engine performance. > The Sightly JSP [performance > tests|https://github.com/apache/sling/blob/trunk/bundles/scripting/sightly/testing-content/src/main/resources/SLING-INF/apps/sightlyperf/test/test.jsp] > show a 5x degradation on my machine when compared to running the same tests > on {{org.apache.sling.scripting.jsp}} 2.1.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)