Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 17 May 2011 09:28:47 +0000 (UTC)
From: "Earwin Burrfoot (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1867462454.18560.1305624527359.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1276268848.17030.1305584267724.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (LUCENE-3105) String.intern() calls slow down
 IndexWriter.close() and IndexReader.open() for index with large number of
 unique field names
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034640#comment-13034640 ] 

Earwin Burrfoot commented on LUCENE-3105:
-----------------------------------------

Hmm.. Ok, it *is* still used, but that's gonna be fixed, mm?

> String.intern() calls slow down IndexWriter.close() and IndexReader.open() for index with large number of unique field names
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3105
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3105
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 3.1
>            Reporter: Mark Kristensson
>         Attachments: LUCENE-3105.patch
>
>
> We have one index with several hundred thousand unqiue field names (we're optimistic that Lucene 4.0 is flexible enough to allow us to change our index design...) and found that opening an index writer and closing an index reader results in horribly slow performance on that one index. I have isolated the problem down to the calls to String.intern() that are used to allow for quick string comparisons of field names throughout Lucene. These String.intern() calls are unnecessary and can be replaced with a hashmap lookup. In fact, StringHelper.java has its own hashmap implementation that it uses in conjunction with String.intern(). Rather than using a one-off hashmap, I've elected to use a ConcurrentHashMap in this patch.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org