lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34930] - [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources
Date Tue, 24 May 2005 06:14:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34930>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34930





------- Additional Comments From whoschek@lbl.gov  2005-05-24 08:14 -------
Most likely the IOExceptions stem from FastCharStream of StandardAnalyzer, at least that's
my experience. 
See the header of your hprof file to check if that's the case.

Javacc has a gotcha in that it "likes" IOExceptions as part of the normal control flow on
stream termination.
I have performance patches for this that make FastCharStream 2-10 times faster for small inputs
(it 
doesn't matter on large inputs), but I never bothered submitted them since they were not crucial
for me, 
and seeing that most submissions to lucene-dev go into a black hole anyway without any response,

neither negative or positive, simply ignored... Hint :-)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message