It is an expected behaviour inhereted from Lucene.Java and I haven't seen a (remarkable) performance degrade because of this.
DIGY. -----Original Message----- From: Ron Grabowski [mailto:rongrabow...@yahoo.com] Sent: Saturday, October 31, 2009 12:52 AM To: lucene-net-user@incubator.apache.org Subject: Re: Excessive IOExceptions in IndexSearcher/QueryParser/FastCharStream? I'm using https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_4_0/ src/Lucene.Net. ----- Original Message ---- From: Ron Grabowski <rongrabow...@yahoo.com> To: lucene-net-user@incubator.apache.org Sent: Fri, October 30, 2009 6:44:34 PM Subject: Excessive IOExceptions in IndexSearcher/QueryParser/FastCharStream? I was profiling my search code and saw an awful lot of Exceptions being throw for simple usages of QueryParser: http://www.ronosaurus.com/lucene/indexsearcher_queryparser_ioexception.png For example this code produces 2 IOExceptions in FastCharStream (line 25): QueryParser parser = new QueryParser("name", new StandardAnalyzer()); parser.Parse("produce"); Is that normal? In my screenshot there's close to 100 Exceptions within 15 seconds of running some threaded searches. Would the FastCharStream be faster if it didn't throw so many Exceptions? I tried hacking CanRead() into CharStream but didn't get very far.
