[
https://issues.apache.org/jira/browse/JCRVLT-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054570#comment-18054570
]
Joerg Hoh commented on JCRVLT-831:
----------------------------------
[~reschke] Towards you point 5:
bq. A simple change would be to always serialize the whole namespace registry.
That would avoid all scanning, but it would affect the size of the generated
XML. As compromise, that shortcut could be restricted to the case where we
actually have ordered collections.
I like that idea.
We could limit that to ordered child lists exceeding a certain size (number of
siblings); we could use OAK-11731 to check that number easily whenever we
encounter an orderable node; the less efficient alternative would be to start
iterating until that threshold.
> For collection of namespace prefixes, avoid iterating over sibling nodes not
> contained in the filter(s)
> -------------------------------------------------------------------------------------------------------
>
> Key: JCRVLT-831
> URL: https://issues.apache.org/jira/browse/JCRVLT-831
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Fix For: 4.2.0
>
>
> It appears that the changes for JCRVLT-789 improved the performance for
> exporting the *content*, however the phase of collecting namespace prefixes
> does not use that optimzation.
> (TBD: write a test)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
