lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guido Medina <>
Subject Re: Memory Impact of a New Core
Date Tue, 23 Apr 2013 11:25:18 GMT
I'm not an expert, but at some extent I think it will come down to few 

  * How much data is been cached per core.
  * If memory is an issue and still you want performance, I/O with low
    cache could be an issue (SSDs?)
  * Soft commits which implies open searchers per soft commit (and per
    core) will depend on caches.

I do believe at the end it will be a direct result of your caching and 
I/O. If all you care is performance, caching (memory) could be replaced 
with faster I/O though soft commits will be fragile to memory due to its 
nature (depends on caching/memory and low I/O usage)

Hope I made sense, I probably tried too many points of view in a single 


On 23/04/13 11:50, Jérôme Étévé wrote:
> Hi all,
> We've got quite a lot of (mostly small) solr cores in our Solr instance.
> They all share the same solrconfig.xml and schema.xml (only the data
> differs).
> I'm wondering how far can I go in terms of number of cores. CPU is not an
> issue, but memory could be.
> An idea/guideline about the impact of a new Solr Core in a Solr instance?
> Thanks!
> Jerome.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message