Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <14441378.141311277931229365.JavaMail.jira@thor>
Date: Wed, 30 Jun 2010 16:53:49 -0400 (EDT)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2669) Improve reading of cached UUID for given
 document number
In-Reply-To: <28066123.141301277930989337.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcel Reutegger updated JCR-2669:
----------------------------------

    Attachment: JCR-2669.patch

Proposed patch.

The test case shows that the custom field is 25 times faster.

> Improve reading of cached UUID for given document number
> --------------------------------------------------------
>
>                 Key: JCR-2669
>                 URL: https://issues.apache.org/jira/browse/JCR-2669
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>         Attachments: JCR-2669.patch
>
>
> CachingIndexReader.document(int n, FieldSelector fieldSelector) creates a new
> Field from the cached UUID. The lucene Field implementation always does a
> String.intern() on the field name, which is quite slow. We should probably have
> our own implementation for that specific use case where we know that the name
> is already interned. e.g. UUIDField implements Fieldable.

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