You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joel Richard (JIRA)" <ji...@apache.org> on 2015/03/27 13:29:53 UTC
[jira] [Resolved] (SLING-4532) Performance: DefaultSlingScript has
too much overhead
[ https://issues.apache.org/jira/browse/SLING-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joel Richard resolved SLING-4532.
---------------------------------
Resolution: Invalid
Closing because the overhead is added in a BindingsValuesProvider which is called in DefaultSlingScript.verifySlingBindings and not in DefaultSlingScript itself.
> Performance: DefaultSlingScript has too much overhead
> -----------------------------------------------------
>
> Key: SLING-4532
> URL: https://issues.apache.org/jira/browse/SLING-4532
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Core 2.0.28
> Reporter: Joel Richard
> Labels: performance
> Attachments: measure.patch
>
>
> While I was profiling a slow page, I saw that a significant amount of time is spent inside DefaultSlingScript. Since profilers often cannot be trusted, I added some code (see attachment) to measure the time spent without the script execution itself (JSP in my case) and came to 8% of the whole page rendering time. Since the JSP itself has been compiled before the measurements, I would have expected the overhead clearly below 1%.
> The page which I profiled has about 100 sling includes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)