We have kept a 72 CPU machine busy with a single Solr process, so I doubt that multiple processes are needed.
The big question is the size of the index. If it is too big to fit in RAM (OS file buffers), then the system is IO bound and CPU doesn’t really matter. Everything will depend on the speed and capacity of the disk system. If the index does fit in RAM, then you should be fine. You may want to spend some effort on reducing index size if it is near the limit. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 6, 2022, at 8:18 AM, Gus Heck <gus.h...@gmail.com> wrote: > > It depends... on your data, on your usage, etc. The best answers are > obtained by testing various configurations, if possible by replaying > captured query load from production. There is (for all java programs) an > advantage to staying under 32 GB RAM, but without an idea of the number of > machines you describe, the size of the corpus (docs and disk) and what your > expected usage patterns are (both indexing and query) one can't say if you > need more heap than that, either in one VM or across several VMs. > > To understand how "unallocated" memory not assigned to the java heap (or > other processes) is utilized to improve search performance, this article is > helpful: > https://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html > > -Gus > > On Thu, Oct 6, 2022 at 8:31 AM matthew sporleder <msporle...@gmail.com> > wrote: > >> Why do you want to split it up at all? >> >> On Thu, Oct 6, 2022 at 3:58 AM Dominique Bejean >> <dominique.bej...@eolya.fr> wrote: >>> >>> Hi, >>> >>> One of our customer have huge servers >>> >>> - Bar-metal >>> - 64 CPU >>> - 512 Gb RAM >>> - 6x2Tb disk in RAID 6 (so 2Tb disk space available) >>> >>> >>> I think the best way to optimize resources usage of these servers is to >>> install several Solr instances. >>> >>> I imagine 2 scenarios to be tested according to data volumes, update >> rate, >>> request volume, ... >>> >>> Do not configure disks in RAID 6 but, leave 6 standard volumes (more >> space >>> disk, more I/O available) >>> Install 3 or 6 solr instances each one using 1 ou 2 disk volumes >>> >>> Obviously, replicate shards and verify replicates of a shard are not >>> located on the same physical server. >>> >>> What I am not sure is how MMapDirectory will work with several Solr >>> instances. Will off heap memory correctly managed and shared between >>> several Solr instances ? >>> >>> Thank you for your advice. >>> >>> Dominique >> > > > -- > http://www.needhamsoftware.com (work) > http://www.the111shift.com (play)
