lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: Lucene Search and Disk I/O
Date Fri, 20 Dec 2013 17:53:21 GMT
The situation is pretty much the same as before, just different file names :)

Lucene pre-loads certain "hot" structures into RAM: the terms index
(.tip files), deleted documents (.del files), norms, etc.

For all other files, it relies on the OS to cache any hot pages in its
buffer/IO cache, and it typically reads sequentially so OS readahead
should work well.

Mike McCandless

On Fri, Dec 20, 2013 at 1:10 AM, wactioner <> wrote:
> I had a similar question posted  here
> <>
> a few years earlier.
> How does a lucene search handle disk I/O and reading from index files? I'm
> not sure how much the previous answer stands true. I notice that some of the
> index files referenced in the last answer (.tii files) don't exist anymore,
> unless .tii files were renamed to .tip.
> If anyone is familiar with the matter on this board, could you comment on
> how ElasticSearch shards these files? Any thoughts would be appreciated.
> Thank you!
> --
> View this message in context:
> Sent from the Lucene - Java Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message