Hi All, Something we learned recently that might be useful to the community.
We're running solr in docker, and we've constrained each of our containers to have access to 10G of the host's ram. Also, through `docker stats`, we can see the Block IO (filesystem reads/writes) that the solr process is doing. On a test system with three nodes, three shards, each with two NRT replicas, and indexing a reference set of a million documents: - When allocating half of the container's available ram to the jvm (i.e. starting solr with -m 5g) we see a read/write distribution of roughly 400M/2G on each solr node. - When allocation ALL of the container's available ram to the jvm (i.e. starting solr with -m 10g) we see a read/write distribution of around 10G / 2G on each solr node, and the latency on the underlying disk soars. The takeaway here is that Solr really does need non-jvm RAM to function, and if you're having performance issues, "adding more ram to the jvm" isn't always the right way to get things going faster. Best, Kyle
