[jira] [Created] (SLING-11608) Cache script dependency resolution

2022-10-03 Thread Radu Cotescu (Jira) 
Radu Cotescu created SLING-11608:


 Summary: Cache script dependency resolution
 Key: SLING-11608
 URL: https://issues.apache.org/jira/browse/SLING-11608
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Engine 1.4.22-1.4.0


Up to version 1.4.20-1.4.0 of the HTL Script Engine, the 
[ScriptUtils|https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/org.apache.sling.scripting.sightly-1.4.20-1.4.0/src/main/java/org/apache/sling/scripting/sightly/impl/utils/ScriptUtils.java]
 class walked the resource tree to solve the correct HTL Template/script 
provided by another script engine based on the resource tree. However, in 
situations where the script tree is stable (e.g. systems that have a read-only 
search path, systems that deploy script exclusively via bundled scripts, etc.), 
it makes sense to cache this resolution.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SLING-11607) Emit metric on the time that a package spends in the journal

2022-10-03 Thread Timothee Maret (Jira) 


[ 
https://issues.apache.org/jira/browse/SLING-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612416#comment-17612416
 ] 

Timothee Maret commented on SLING-11607:


Merged 
[https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/112,]
 thank you!

> Emit metric on the time that a package spends in the journal
> 
>
> Key: SLING-11607
> URL: https://issues.apache.org/jira/browse/SLING-11607
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.28
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> We should emit a metric that calculates the time in milliseconds that a 
> package spends in the journal.
>  
> We already have a metric called {{request_distributed_duration}} that tracks 
> the time since a package is enqueued until it is successfully imported. 
> However, since this timer includes the import of the package content, we are 
> not measuring the latency in the journal.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (SLING-11607) Emit metric on the time that a package spends in the journal

2022-10-03 Thread Timothee Maret (Jira) 


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

Timothee Maret reassigned SLING-11607:
--

Assignee: José Correia

> Emit metric on the time that a package spends in the journal
> 
>
> Key: SLING-11607
> URL: https://issues.apache.org/jira/browse/SLING-11607
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.28
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> We should emit a metric that calculates the time in milliseconds that a 
> package spends in the journal.
>  
> We already have a metric called {{request_distributed_duration}} that tracks 
> the time since a package is enqueued until it is successfully imported. 
> However, since this timer includes the import of the package content, we are 
> not measuring the latency in the journal.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (SLING-11607) Emit metric on the time that a package spends in the journal

2022-10-03 Thread Jira 
José Correia created SLING-11607:


 Summary: Emit metric on the time that a package spends in the 
journal
 Key: SLING-11607
 URL: https://issues.apache.org/jira/browse/SLING-11607
 Project: Sling
  Issue Type: Improvement
  Components: Content Distribution
Reporter: José Correia
 Fix For: Content Distribution Journal Core 0.1.28


We should emit a metric that calculates the time in milliseconds that a package 
spends in the journal.

 

We already have a metric called {{request_distributed_duration}} that tracks 
the time since a package is enqueued until it is successfully imported. 
However, since this timer includes the import of the package content, we are 
not measuring the latency in the journal.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)