Home/ Questions/Q 7400737
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T04:17:39+00:00

I am using a read-only Lucene.NET index in a web application and creating a

  • 0

I am using a read-only Lucene.NET index in a web application and creating a single IndexSearcher for all requests. The creation process for this is thread-safe, as are the IndexSearcher methods according to the docs.

My question is around how the IndexSearcher stores the index in memory after opening. Does it read the entire index into memory on creation?

I ask because the application uses (potentially) hundreds of different indices, at approx. 27MB (on disk) each, with a new IndexSearcher for every one. I want to be aware of how this will affect the memory usage of the worker process.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The IndexSearcher will not store the entire index in memory, but it’s underlying reader caches some information about Fields, Terms and Segments. The amount of memory required will vary a lot depending of what’s in your index, etc.

    Using a really high amount of indices like that will affect total memory consumed by the process. It is generally better to have fewer bigger indices.

    If you intend to use several hundred indices, I would recommend to test the scalability of your approach with real production data first.

    • 0