You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2015/07/08 19:07:04 UTC
[jira] [Commented] (SLING-4866) JSP scripting engine performance
degraded in org.apache.sling.scripting.jsp 2.1.6
[ https://issues.apache.org/jira/browse/SLING-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618945#comment-14618945 ]
Radu Cotescu commented on SLING-4866:
-------------------------------------
[~cziegeler], could we somehow maintain the compilation consistency without imposing such a slow locking mechanism?
> 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=r1629144] 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)