lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments
Date Fri, 26 Mar 2010 18:38:28 GMT


Michael McCandless commented on LUCENE-2324:

bq. I was thinking we were going to do that... having a fixed number of DocumentsWriterPerThread
instances, and a ThreadBinder that let's a thread wait if the perthread is not available.
You don't need to interleave docIds then?

I think we'd have a fixed max?  And then we'd create a new DW when all existing ones are in-use
and we're not yet at the max?

Eg if it's a thread pool of size 50 that's indexing, but, the rate of docs is very slow such
that in practice only one of these 50 threads is indexing at once, we'd only use one DW. 
And we'd flush when that DW hits the RAM limit.

> Per thread DocumentsWriters that write their own private segments
> -----------------------------------------------------------------
>                 Key: LUCENE-2324
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Minor
>             Fix For: 3.1
> See LUCENE-2293 for motivation and more details.
> I'm copying here Mike's summary he posted on 2293:
> Change the approach for how we buffer in RAM to a more isolated
> approach, whereby IW has N fully independent RAM segments
> in-process and when a doc needs to be indexed it's added to one of
> them. Each segment would also write its own doc stores and
> "normal" segment merging (not the inefficient merge we now do on
> flush) would merge them. This should be a good simplification in
> the chain (eg maybe we can remove the *PerThread classes). The
> segments can flush independently, letting us make much better
> concurrent use of IO & CPU.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message