You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2008/09/01 20:56:44 UTC

[jira] Assigned: (TAPESTRY-2635) possible ognl cache problem

     [ https://issues.apache.org/jira/browse/TAPESTRY-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Schulte reassigned TAPESTRY-2635:
----------------------------------------

    Assignee: Marcus Schulte

> possible ognl cache problem
> ---------------------------
>
>                 Key: TAPESTRY-2635
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2635
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 4.1.5
>         Environment: linux fedora 4, jDK 1.6_05, Tomcat 6.0.13, Ognl 2.7.2
>            Reporter: denis queffeulou
>            Assignee: Marcus Schulte
>
> I'm making some profiling on an web app made with Tapestry 4.1.5 which returns XML.
> In JProfiler, I found that OGNL expressions compilation uses 40% of processing time.
> As the JMeter script is requesting always the same page on the webapp, I'm wondering why the expressions are always compiled. The cache seems not to be used:
> 31896 invocations on ExpressionCache.getCompiledExpression
> 31140 invocations on Ognl.compileExpression
> Another test with 5 pages after 2 hours:
> 34,2% 90528 invocations on ExpressionCache.getCompiledExpression
> 25,4% 90300 invocations on Ognl.compileExpression
> My WAR is a big application, I can't put it here.
> To reproduce, a single page with OGNL should be sufficent. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org