On Thu, Jun 12, 2008 at 12:14 PM, Otis Gospodnetic
<[EMAIL PROTECTED]> wrote:
> That's my observations, too. Shows up more when you have lots of deleted
> docs and high query rates, of course.
Luckily for normal term queries, isDeleted() isn't called.
SegmentTermDocs keeps a reference of the del
(> 1 year ago).
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Yonik Seeley <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Thursday, June 12, 2008 11:08:52 AM
> Subject: Re: Synchronization bottlenecks
&g
On Thu, Jun 12, 2008 at 11:00 AM, Jason Rutherglen
<[EMAIL PROTECTED]> wrote:
> Are there any other unnecessary synchronization points related to
> IndexReader?
IMO, isDeleted() is the only one of any significance for normal
servers (4CPUs or so).
-Yonik
-
I have seen this discussed before but with no conclusion. It is safe to say
that SegmentReader.isDeleted is a synchronization bottleneck. When using a
single IndexReader per query for highly concurrent application such as a web
application, with the index entirely in the system cache, the maximum
