lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dizh@neusoft.com" <d...@neusoft.com>
Subject Re: Performance StringCoding.decode
Date Tue, 05 Aug 2014 15:41:54 GMT
how to monitor? use jprofile?




 
From: Sascha Janz
Date: 2014-08-05 22:36
To: java-user@lucene.apache.org
Subject: Performance StringCoding.decode
hi,
 
i want to speed up our search performance. so i run test and monitor them with java mission
control.
 
the analysis showed that one hotspot is 
 
 
sun.nio.cs.UTF_8$Decoder.decode(byte[], int, int, char[])
- java.lang.StringCoding.decode(Charset, byte[], int, int)
   - java.lang.String.<init>(byte[], int, int, Charset) 
     -org.apache.lucene.codecs.compressing.CompressingStoredFieldsReader.readField(DataInput,

      StoredFieldVisitor, FieldInfo, int)
      -org.apache.lucene.codecs.compressing.CompressingStoredFieldsReader.visitDocument(int,
       StoredFieldVisitor)
       -org.apache.lucene.index.SegmentReader.document(int, StoredFieldVisitor)
        -org.apache.lucene.index.IndexReader.document(int, Set)
 
we use jdk 1.7.55 and lucene 4.9.0.
 
is there a chance to speed this up? or do some changes in lucene IndexWriterConfig, e.g. use
an other codec?
 
we use the default values of IndexWriterConfig
 
 
regards
sascha
 
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
 
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)

is intended only for the use of the intended recipient and may be confidential and/or privileged
of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or
copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please

immediately notify the sender by return e-mail, and delete the original message and all copies
from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message