[jira] [Updated] (OAK-10804) Indexing job: optimize check for hidden nodes

2024-05-15 Thread Nuno Santos (Jira)


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

Nuno Santos updated OAK-10804:
--
Description: 
While downloading the repository from Mongo, the indexing job has to discard 
hidden entries. This is being done by a call to 
{{{}NodeStateUtils.isHiddenPath(){}}}. This call is rather expensive, as it 
creates an iterator over the path segments, which requires creating a new 
string for each path segment. As the indexing job has to check every entry to 
verify if it is hidden, this creates a significant overhead.

The implementation of checking for hidden paths can be replaced by a simple 
search for {{"/:"}} in the string representing the path, which requires no 
object allocation and should therefore be much faster.

  was:
While downloading the repository from Mongo, the indexing job has to discard 
hidden entries. This is being done by a call to 
`NodeStateUtils.isHiddenPath()`. This call is rather expensive, as it creates 
an iterator over the path segments, which requires creating a new string for 
each path segment. As the indexing job has to check every entry to verify if it 
is hidden, this creates a significant overhead.

The implementation of checking for hidden paths can be replaced by a simple 
search for {{"/:"}} in the string representing the path, which requires no 
object allocation and should therefore be much faster.


> Indexing job: optimize check for hidden nodes
> -
>
> Key: OAK-10804
> URL: https://issues.apache.org/jira/browse/OAK-10804
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
>
> While downloading the repository from Mongo, the indexing job has to discard 
> hidden entries. This is being done by a call to 
> {{{}NodeStateUtils.isHiddenPath(){}}}. This call is rather expensive, as it 
> creates an iterator over the path segments, which requires creating a new 
> string for each path segment. As the indexing job has to check every entry to 
> verify if it is hidden, this creates a significant overhead.
> The implementation of checking for hidden paths can be replaced by a simple 
> search for {{"/:"}} in the string representing the path, which requires no 
> object allocation and should therefore be much faster.



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


[jira] [Updated] (OAK-10804) Indexing job: optimize check for hidden nodes

2024-05-15 Thread Nuno Santos (Jira)


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

Nuno Santos updated OAK-10804:
--
Summary: Indexing job: optimize check for hidden nodes  (was: Indexing job: 
optimize check for if a node is hidden)

> Indexing job: optimize check for hidden nodes
> -
>
> Key: OAK-10804
> URL: https://issues.apache.org/jira/browse/OAK-10804
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
>
> While downloading the repository from Mongo, the indexing job has to discard 
> hidden entries. This is being done by a call to 
> `NodeStateUtils.isHiddenPath()`. This call is rather expensive, as it creates 
> an iterator over the path segments, which requires creating a new string for 
> each path segment. As the indexing job has to check every entry to verify if 
> it is hidden, this creates a significant overhead.
> The implementation of checking for hidden paths can be replaced by a simple 
> search for {{"/:"}} in the string representing the path, which requires no 
> object allocation and should therefore be much faster.



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