[
https://issues.apache.org/jira/browse/SLING-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962832#comment-16962832
]
Radu Cotescu commented on SLING-8814:
-------------------------------------
If you're only interested in Java code compilation it should be enough. The HTL
compilers take an HTL script and generate Java code from it, followed by a
compilation of that code. However, this can be seen as an atomic operation [0].
[0] -
https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/org.apache.sling.scripting.sightly-1.2.0-1.4.0/src/main/java/org/apache/sling/scripting/sightly/impl/engine/compiled/SlingHTLMasterCompiler.java#L197
> Create metrics for number of compilations
> -----------------------------------------
>
> Key: SLING-8814
> URL: https://issues.apache.org/jira/browse/SLING-8814
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Commons Compiler 2.3.8
>
>
> A high number of compilations can impact the system performance negatively.
> Additionally, there may be scenarios where compilation should never have
> happened, e.g. scripts were precompiled using Maven tooling or a warmup phase
> was executed.
> We should track the number of compilation events as a metrics to expose these
> kinds of issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
