On 12/6/22 05:08, Joe Jones (DHCW - Software Development) wrote:
Workaround tested and no difference with or without it. New cloud set up with 1200mb heap for each instance and 32gb system RAM on each server. I'm seeing just over 20gb in system cache. Anti-virus exclusions applied and system doesn't appear to be swapping unnecessarily.
A 1.2gb heap sounds extremely small for dealing with millions of documents, even if each node only handles one shard. I'd be curious what your GC logs might reveal.
Cloud was designed some time ago by design architects and under Solr 5.4.1 has been running perfectly fine. This is in use 24/7 so I can't test what it is like when idle. I can only assume at the time the 4 nodes per server was to leverage the 4 CPU's allocated to each machine.
If Solr were a single-threaded application, this might make some sense. But Solr is heavily multithreaded, there is no need to have multiple nodes per machine to take full advantage of a multi-CPU system. With multiple nodes, you're actually more likely to have problems with too many threads competing for CPU resources because each node has no insight into the other nodes.
Thanks, Shawn
