jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2025) Optimize concurrent queries
Date Wed, 29 Apr 2009 08:32:30 GMT

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

Jukka Zitting updated JCR-2025:

    Fix Version/s:     (was: core-1.4.10)

> Optimize concurrent queries
> ---------------------------
>                 Key: JCR-2025
>                 URL: https://issues.apache.org/jira/browse/JCR-2025
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.6.0
>         Attachments: JCR-2025.patch
> There are a number of bottlenecks that prevent scalability of concurrent queries:
> - Fake norms are created repeatedly because a new SearchIndex$CombinedIndexReader is
created for each query. This prevents caching of fake norms on the level of the CombinedIndexReader.
Creating fake norms for index readers that span multiple sub reader is inefficient and should
be avoided. Like with other Jackrabbit specific queries, there should be one for TermQuery,
which is aware of sub readers. Its weight should then create one scorer for each sub reader.
This effectively reuses the fake norms on the sub reader.
> - There should be a  UUID cache that maps document number to UUID. This is basically
the inverse of the existing DocNumberCache. UUID lookup is regularly a bottleneck in the SegmentReader
where the method document() is synchronized and does I/O.
> - Queries often contain constraints that limit the result to nodes with a certain flag
set to a literal. These constraints should be cached in the query handler.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message